Information Disclosure in apache-airflow (CVE-2026-25219)
Summary
Vulnerability in apache-airflow (CVE-2026-25219). Confidential information can be exposed externally. Exploitable via access_key. Mitigation: upgrade to 3.1.8 or later.
Original description
The description as published by the source.
The access_key and connection_string connection properties were not marked as sensitive names in secrets masker. This means that user with read permission could see the values in Connection UI, as well as when Connection was accidentaly logged to logs, those values could be seen in the logs. Azure Service Bus used those properties to store sensitive values. Possibly other providers could be also affected if they used the same fields to store sensitive data.
If you used Azure Service Bus connection with those values set or if you have other connections with those values storing sensitve values, you should upgrade Airflow to 3.1.8
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-25219 has been found in apache-airflow.
Attackers can target a specific entry point like access_key over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade apache-airflow to 3.1.8 or later.
If unsure, ask your IT team or search "apache-airflow CVE-2026-25219" on the vendor's site.
CVE-2026-25219 (apache-airflow) — CWE-200
Attack vector: remote (network-reachable) / no user interaction
Attack surface: access_key / connection_string
Patched: 3.1.8 — 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.
Information disclosure (CWE-200) exists in apache-airflow. Attackers reach the vulnerable code path via access_key.
Check the vendor advisory for the affected versions of apache-airflow. Attack surface: access_key / connection_string.
Severity: ?. Confidential information can be exposed externally.
Update to 3.1.8.
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.1.8ステージング環境で 3.1.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- patch github.com
- web openwall.com
- web pypi.python.org