ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-41017

Apache Airflow's set the JWT auth cookie without the flag, so deployments running the Airflow API server behind an HTTPS-terminating reverse proxy (e.g.

Published Jun 1, 2026 · catalog updated Jul 21, 2026 · the affected product

Check if you run it

No confirmed exploitation is on record for CVE-2026-41017. EPSS is 0.38%. Act only if a listed version of the affected product is installed.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.38%
Remediation
Advisory link
Affected products
cpe apache/airflow

Apache Airflow's set the JWT auth cookie without the flag, so deployments running the Airflow API server behind an HTTPS-terminating reverse proxy (e.g. nginx / Envoy / a managed load balancer that terminates TLS and forwards plaintext to the API server, the default cloud-native topology) would have the user's session JWT replayed over any cleartext HTTP request to the same host. A network-positioned attacker (Wi-Fi MITM, hostile LAN, captive-portal proxy) could induce a logged-in user's browser to issue an HTTP request to the deployment's hostname and capture the JWT cookie out of that request, then replay it against the authenticated API. Affects deployments where the Airflow API server is reached through a TLS-terminating proxy and the cookie's secure-by-default protection is load-bearing for session integrity. Users are advised to upgrade to 3.2.2 or later.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe apache/airflowversion unspecified

How to fix CVE-2026-41017

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-41017. EPSS is 0.38%. Act only if a listed version of the affected product is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-614. EPSS 0.38%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Nginx security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 1, 2026 · NIST NVD

    Detected

    Apache Airflow's set the JWT auth cookie without the flag, so deployments running the Airflow API server behind an HTTPS-terminating reverse proxy (e.g. nginx / Envoy / a managed load balancer that terminates TLS and forwards plaintext to the API server, the default cloud-native topology) would have the user's session JWT replayed over any cleartext HTTP request to the same host. A network-positio

  2. Jul 21, 2026 · NIST NVD

    Updated

    Apache Airflow's set the JWT auth cookie without the flag, so deployments running the Airflow API server behind an HTTPS-terminating reverse proxy (e.g. nginx / Envoy / a managed load balancer that terminates TLS and forwards plaintext to the API server, the default cloud-native topology) would have the user's session JWT replayed over any cleartext HTTP request to the same host. A network-positio

Sources

  • CVE.orgVulnerability recordCVE-2026-41017

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-41017

    30-day exploitation probability 0.4%

    first.org
  • NIST NVDVulnerability recordCVE-2026-41017

    Apache Airflow's set the JWT auth cookie without the flag, so deployments running the Airflow API server behind an HTTPS-terminating reverse proxy (e.g. nginx / Envoy / a managed load balancer that terminates TLS and forwards plaintext to the API s

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.