CVE-2026-41017
Apache Airflow's `JWTRefreshMiddleware` set the JWT auth cookie …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/apache/airflow/pull/65348
- lists.apache.org/thread/9jx0sk49c1250zflx0q3clc717qgjdch
- www.openwall.com/lists/oss-security/2026/05/31/6
- nvd.nist.gov/vuln/detail/CVE-2026-41017
- github.com/pypa/advisory-database/tree/main/vulns/apache-airflow/PYSEC-2026-171.yaml
- github.com/advisories/GHSA-95v7-h9j5-gvjr
- nvd.nist.gov/vuln/detail/CVE-2026-41017
- cve.org/CVERecord?id=CVE-2026-41017
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.