Open Redirect in airflow (CVE-2026-40961)
Summary
Vulnerability in airflow (CVE-2026-40961). Risk of unauthorized operations or information disclosure. Exploitable via is_safe_url. Mitigation: upgrade to 3.2.2 or later.
Original description
The description as published by the source.
A bug in the login redirect route in Apache Airflow allowed authenticated users to craft URLs that bypassed the is_safe_url check, enabling redirection from a trusted Airflow domain to an attacker-controlled origin. Users are advised to upgrade to apache-airflow 3.2.2 or later. As a defense-in-depth mitigation, deployment operators can place Airflow behind a reverse proxy that strips off-domain next= query parameters before they reach the login endpoint.
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-40961 has been found in airflow.
Attackers can target a specific entry point like is_safe_url over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.2/10.
What to do: upgrade airflow to 3.2.2 or later.
If unsure, ask your IT team or search "airflow CVE-2026-40961" on the vendor's site.
CVE-2026-40961 (airflow) — CWE-601 / CVSS v3 7.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: is_safe_url
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-601) exists in airflow. Attackers reach the vulnerable code path via is_safe_url without authentication.
Check the vendor advisory for the affected versions of airflow. Attack surface: is_safe_url.
Severity: High (CVSS 7.2/10). Risk of unauthorized operations or information disclosure.
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 '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 'airflow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
airflowを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade 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 pypi.python.org