Advisory

PYSEC-2026-171

Also known as: BIT-airflow-2026-41017, CVE-2026-41017, GHSA-95v7-h9j5-gvjr

Summary

The record has no summary.

Details

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.

Severity

Medium Basis: CVSS v3 score 5.9, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Dates

Published
2026-06-01 09:16 UTC
Modified
2026-07-13 16:45 UTC

Affected packages and fixes

apache-airflow

PyPI · All systems

Affected

  • introduced 3.0.0, fixed 3.2.2 (ecosystem)

Fixed versions

3.2.2

Fix

  • Fixed version 3.2.2
    pip install --upgrade apache-airflow==3.2.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences