Vulnerability in apache-airflow (CVE-2026-40861)
Summary
Vulnerability in apache-airflow (CVE-2026-40861). Confidential information can be exposed externally. Exploitable via airflow.cfg. Mitigation: upgrade to 3.2.2 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-40861 has been found in apache-airflow.
Attackers can target a specific entry point like airflow.cfg over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade apache-airflow to 3.2.2 or later.
If unsure, ask your IT team or search "apache-airflow CVE-2026-40861" on the vendor's site.
CVE-2026-40861 (apache-airflow) — CWE-59 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: airflow.cfg / task_id / KEY_REGEX / base_log_folder
Patched: 3.2.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-59) exists in apache-airflow. Attackers reach the vulnerable code path via airflow.cfg.
Check the vendor advisory for the affected versions of apache-airflow. Attack surface: airflow.cfg / task_id / KEY_REGEX / base_log_folder.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 3.2.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'apache-airflow' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'apache-airflow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
apache-airflowを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade apache-airflow to 3.2.2ステージング環境で 3.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory lists.apache.org
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web openwall.com
- web github.com
- web pypi.python.org