Apache Airflow has a Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

TRUNG BÌNH 5.9CVE-2026-41017 · BIT-airflow-2026-41017 · GHSA-95v7-h9j5-gvjr · Công bố 01/06/2026 · cập nhật 21/07/2026

Tóm tắt nhanh

CVE-2026-41017 là lỗ hổng mức TRUNG BÌNH (CVSS 5.9) ảnh hưởng apache-airflow, airflow (apache).
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.35%, cao hơn 28.7% các lỗ hổng khác.
Cách xử lý: cập nhật lên 3.2.2 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
apache-airflow PyPI	`≥ 3.0.0, < 3.2.2`	`3.2.2`
airflow apache	`≥ 3.0.0, < 3.2.2`	`3.2.2`

Mô tả

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.

Mô tả của NVD

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.