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.
A Dag author could either (a) create a symlink under their task's log directory pointing to an arbitrary file readable by the API server process (read-path attack — e.g. `/etc/passwd` or `airflow.cfg`) or (b) supply a `task_id` containing `..` sequences accepted by the Task SDK's `KEY_REGEX` (write-path attack), and in both cases the FileTaskHandler resolves the log path outside the configured `base_log_folder`, leaking or overwriting arbitrary files. Only affects deployments where the worker log folder is shared with the API server. Users are advised to upgrade to `apache-airflow` 3.2.2 or later. As a defense-in-depth mitigation, deploy the worker and API server with separate log volumes so that worker-controlled paths cannot reach the API server's filesystem.
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: Un autor de Dag podría (a) crear un enlace simbólico bajo el directorio de logs de su tarea apuntando a un archivo arbitrario legible por el proceso del servidor API (ataque de ruta de lectura - p. ej. '/etc/pass1d' o 'airflow.cfg') o (b) proporcionar un 'task_id' que contenga secuencias '..' aceptadas por el 'KEY_REGEX' del SDK de Tareas (ataque de ruta de escritura), y en ambos casos el FileTaskHandler resuelve la ruta del log fuera de la 'base_log_folder' configurada, filtrando o sobrescribiendo archivos arbitrarios. Solo afecta a despliegues donde la carpeta de logs del worker es compartida con el servidor API. Se aconseja a los usuarios actualizar a 'apache-airflow' 3.2.2 o posterior. Como mitigación de defensa en profundidad, despliegue el worker y el servidor API con volúmenes de log separados para que las rutas controladas por el worker no puedan alcanzar el sistema de archivos del servidor API.
New CVE Received from Apache Software Foundation6/01/2026 5:16:17 AM
Action
Type
Old Value
New Value
Added
Description
A Dag author could either (a) create a symlink under their task's log directory pointing to an arbitrary file readable by the API server process (read-path attack — e.g. `/etc/passwd` or `airflow.cfg`) or (b) supply a `task_id` containing `..` sequences accepted by the Task SDK's `KEY_REGEX` (write-path attack), and in both cases the FileTaskHandler resolves the log path outside the configured `base_log_folder`, leaking or overwriting arbitrary files. Only affects deployments where the worker log folder is shared with the API server. Users are advised to upgrade to `apache-airflow` 3.2.2 or later. As a defense-in-depth mitigation, deploy the worker and API server with separate log volumes so that worker-controlled paths cannot reach the API server's filesystem.