You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
This CVE record has been updated after NVD enrichment efforts were completed. Enrichment data supplied by the NVD may require amendment due to these changes.
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.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: Apache Airflow de Apache Software Foundation, Description: El 'JWTRefreshMiddleware' de Apache Airflow estableció la cookie de autenticación JWT sin la bandera 'Secure', por lo que las implementaciones que ejecutan el servidor API de Airflow detrás de un proxy inverso con terminación HTTPS (por ejemplo, nginx / Envoy / un balanceador de carga gestionado que termina TLS y reenvía texto plano al servidor API, la topología nativa de la nube predeterminada) tendrían el JWT de la sesión del usuario reproducido sobre cualquier solicitud HTTP en texto claro al mismo host. Un atacante posicionado en la red (MitM de Wi-Fi, LAN hostil, proxy de portal cautivo) podría inducir al navegador de un usuario autenticado a emitir una solicitud HTTP al nombre de host de la implementación y capturar la cookie JWT de esa solicitud, para luego reproducirla contra la API autenticada. Afecta a las implementaciones donde se accede al servidor API de Airflow a través de un proxy con terminación TLS y la protección de la cookie 'segura por defecto' es fundamental para la integridad de la sesión. Se aconseja a los usuarios actualizar a 'apache-airflow' 3.2.2 o posterior.
New CVE Received from Apache Software Foundation6/01/2026 5:16:18 AM
Action
Type
Old Value
New Value
Added
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.