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.
Exploitation requires the attacker to already be an authenticated Airflow worker holding a valid Log-server JWT issued for at least one Dag. Apache Airflow's Log server authorized JWT tokens against Dag IDs by applying Python's `str.lstrip()` to the requested path segment when verifying the JWT's `sub` claim. `str.lstrip()` strips any of a *set* of characters from the left (not a prefix), so a JWT issued for a Dag named e.g. `dag_a` would authorize log access to any other Dag whose name began with any subset of the characters `{d, a, g, _}` (e.g. `dag_attacker`, `aaaa_target`, `_dag_secret`). Such an authenticated worker could enumerate and read worker logs of other Dags whose names happened to share that character-class prefix, leaking task output and error traces beyond the documented per-Dag isolation boundary. Affects deployments relying on per-Dag log-access scoping (multi-team, shared-executor, shared-worker topologies). 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: La explotación requiere que el atacante ya sea un worker de Airflow autenticado que posea un JWT válido del Log-server emitido para al menos un Dag. El Log-server de Apache Airflow autorizaba tokens JWT contra IDs de Dag aplicando 'str.lstrip()' de Python al segmento de ruta solicitado al verificar la 'sub' claim del JWT. 'str.lstrip()' elimina cualquiera de un conjunto de caracteres de la izquierda (no un prefijo), por lo que un JWT emitido para un Dag llamado, por ejemplo, 'dag_a' autorizaría el acceso a los logs de cualquier otro Dag cuyo nombre comenzara con cualquier subconjunto de los caracteres '{d, a, g, _}' (por ejemplo, 'dag_attacker', 'aaaa_target', '_dag_secret'). Dicho worker autenticado podría enumerar y leer los logs de worker de otros Dags cuyos nombres compartieran ese prefijo de clase de caracteres, filtrando la salida de tareas y los rastros de error más allá del límite de aislamiento por Dag documentado. Afecta a las implementaciones que dependen del alcance de acceso a logs por Dag (topologías multi-equipo, de ejecutor compartido, de worker compartido). 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:19 AM
Action
Type
Old Value
New Value
Added
Description
Exploitation requires the attacker to already be an authenticated Airflow worker holding a valid Log-server JWT issued for at least one Dag. Apache Airflow's Log server authorized JWT tokens against Dag IDs by applying Python's `str.lstrip()` to the requested path segment when verifying the JWT's `sub` claim. `str.lstrip()` strips any of a *set* of characters from the left (not a prefix), so a JWT issued for a Dag named e.g. `dag_a` would authorize log access to any other Dag whose name began with any subset of the characters `{d, a, g, _}` (e.g. `dag_attacker`, `aaaa_target`, `_dag_secret`). Such an authenticated worker could enumerate and read worker logs of other Dags whose names happened to share that character-class prefix, leaking task output and error traces beyond the documented per-Dag isolation boundary. Affects deployments relying on per-Dag log-access scoping (multi-team, shared-executor, shared-worker topologies). Users are advised to upgrade to `apache-airflow` 3.2.2 or later.