CVE-2026-41017: Apache Airflow: JWT cookie missing Secure flag in JWTRefreshMiddleware behind HTTPS-terminating proxy
This Apache advisory covers CVE-2026-41017 in Apache Airflow.
- CVE-2026-41017
Key facts
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N· base score 5.9, scored by CISA-ADPAttack vector: network. Attack complexity: high. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.- Weakness
- CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Apache Airflow 3.0.0 before 3.2.2
- Fixed in
- 3.2.2
- Source published
- Source revised
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
Description
Apache Airflow's `JWTRefreshMiddleware` set the JWT auth cookie without the `Secure` 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 `apache-airflow` 3.2.2 or later.
Text from the source record.
- Apache Airflow 3.0.0 before 3.2.2
Official advisory · medium-confidence parse· fetched ·verify at source
How to fix CVE-2026-41017
Upgrade to a fixed release named by Apache:
- 3.2.2
Vendor guidance
- Users are advised to upgrade to `apache-airflow` 3.2.2 or later.
Support dates for the fixed release lines
- Apache Airflow 3.2: support ended
More Apache Software Foundation advisories
CVE-2026-40913Nov 9, 2026Apache Airflow's public Import Errors API returns the raw parse-failure stack trace to anyCVE-2026-50204Nov 9, 2026Apache Airflow's audit log stored Connection and Variable secret values in cleartextCVE-2026-68982Nov 9, 2026Apache Airflow's CeleryExecutor ran callback workloadsCVE-2026-76185Nov 9, 2026Apache Airflow's Task SDK secret cache built its keys from the team name and secret idCVE-2026-86829Nov 9, 2026Apache Airflow's scheduler fully deserializes XCom values written by task codeCVE-2026-82337Nov 9, 2026Apache Airflow rebuilt deadline alert fields through generic deserialization
Apache Software Foundation advisories, June 2026All Apache Software Foundation advisories
Get an email when Apache Airflow publishes the next one.
See Apache Airflow's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
iPhone and Android apps · New on the App Store
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
