CVE-2026-41017

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.

PUBLISHED Reserved 2026-04-16 | Published 2026-06-01 | Updated 2026-06-02 | Assigner apache

Problem types

CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

Product status

Credits

Ran (@eddieran) finder

Jarek Potiuk remediation developer

References

www.openwall.com/lists/oss-security/2026/05/31/6

github.com/apache/airflow/pull/65348 patch

lists.apache.org/thread/9jx0sk49c1250zflx0q3clc717qgjdch vendor-advisory

cve.org (CVE-2026-41017)

nvd.nist.gov (CVE-2026-41017)

Download JSON