Vulnerability in apache-airflow (CVE-2026-68968)
Summary
Vulnerability in apache-airflow (CVE-2026-68968). Confidential information can be exposed externally. Exploitable via backfill_id. Mitigation: upgrade to 3.3.1 or later.
Original description
The description as published by the source.
Apache Airflow's Backfill API authorized a request against a Dag id supplied by the caller whenever the backfill_id path segment failed to parse. The authorization dependency parsed it with int() while the route handler parsed it as pydantic's NonNegativeInt, which accepts values int() rejects (1.0 coerces to 1); FastAPI resolves dependencies before endpoint validation, so the two acted on different Dags. An authenticated user holding edit permission on any single Dag could therefore read, pause and cancel backfills belonging to any other Dag, including moving another Dag's queued runs to failed. No non-default configuration is required and backfill ids are sequential, so finding a target is trivial. Users are advised to upgrade to apache-airflow 3.3.1 or later, which parses the backfill id with the same type the routes declare.
Source: NIST National Vulnerability Database 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-68968 has been found in apache-airflow.
Attackers can target a specific entry point like backfill_id over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade apache-airflow to 3.3.1 or later.
If unsure, ask your IT team or search "apache-airflow CVE-2026-68968" on the vendor's site.
CVE-2026-68968 (apache-airflow) — CWE-436 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: backfill_id / NonNegativeInt / failed
Patched: 3.3.1 — 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-436) exists in apache-airflow. Attackers reach the vulnerable code path via backfill_id without authentication.
Check the vendor advisory for the affected versions of apache-airflow. Attack surface: backfill_id / NonNegativeInt / failed.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 3.3.1.
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.3.1ステージング環境で 3.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web lists.apache.org
- web openwall.com
- web github.com
- web github.com
- web github.com
- web github.com