CVE-2026-40861: CWE-59: Improper Link Resolution Before File Access ('Link Following') in Apache Software Foundation Apache Airflow
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.
AI Analysis
Technical Summary
This vulnerability involves improper link resolution before file access (CWE-59) in Apache Airflow's FileTaskHandler. A DAG author can create symbolic links or use specially crafted task IDs containing '..' sequences that bypass the configured base_log_folder restrictions. This allows the API server process to read or overwrite arbitrary files outside the intended log directory, but only in deployments where the worker log folder is shared with the API server. The vulnerability enables both read-path and write-path attacks, potentially exposing sensitive files like /etc/passwd or airflow.cfg or allowing unauthorized file modifications.
Potential Impact
The impact includes unauthorized disclosure of sensitive files and potential overwriting of arbitrary files on the API server filesystem. This can compromise confidentiality and integrity of the system where the worker log folder is shared with the API server. The vulnerability does not affect deployments with separate log volumes for worker and API server. There are no known exploits in the wild at this time.
Mitigation Recommendations
Users should upgrade to Apache Airflow version 3.2.2 or later, where this vulnerability is addressed. As an additional defense-in-depth measure, deploy the worker and API server with separate log volumes to prevent worker-controlled paths from accessing the API server's filesystem. Patch status is not explicitly confirmed in the provided data, but the vendor advisory recommends upgrading to 3.2.2 or later, indicating an official fix is available.
CVE-2026-40861: CWE-59: Improper Link Resolution Before File Access ('Link Following') in Apache Software Foundation Apache Airflow
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.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability involves improper link resolution before file access (CWE-59) in Apache Airflow's FileTaskHandler. A DAG author can create symbolic links or use specially crafted task IDs containing '..' sequences that bypass the configured base_log_folder restrictions. This allows the API server process to read or overwrite arbitrary files outside the intended log directory, but only in deployments where the worker log folder is shared with the API server. The vulnerability enables both read-path and write-path attacks, potentially exposing sensitive files like /etc/passwd or airflow.cfg or allowing unauthorized file modifications.
Potential Impact
The impact includes unauthorized disclosure of sensitive files and potential overwriting of arbitrary files on the API server filesystem. This can compromise confidentiality and integrity of the system where the worker log folder is shared with the API server. The vulnerability does not affect deployments with separate log volumes for worker and API server. There are no known exploits in the wild at this time.
Mitigation Recommendations
Users should upgrade to Apache Airflow version 3.2.2 or later, where this vulnerability is addressed. As an additional defense-in-depth measure, deploy the worker and API server with separate log volumes to prevent worker-controlled paths from accessing the API server's filesystem. Patch status is not explicitly confirmed in the provided data, but the vendor advisory recommends upgrading to 3.2.2 or later, indicating an official fix is available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-04-15T13:58:24.192Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1d4e71e29bf47b50cd495f
Added to database: 6/1/2026, 9:18:41 AM
Last enriched: 6/1/2026, 9:49:09 AM
Last updated: 6/2/2026, 4:58:40 AM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.