Vulnerability in apache-airflow (CVE-2026-68971)
Summary
Vulnerability in apache-airflow (CVE-2026-68971). Confidential information can be exposed externally. Exploitable via POST /api/v2/assets/{asset_id}/materialize. Mitigation: upgrade to 3.3.1 or later.
Original description
The description as published by the source.
Apache Airflow's asset materialization endpoint (POST /api/v2/assets/{asset_id}/materialize) and the XCom result check on wait_dag_run_until_finished authorized the target Dag without its team, unlike every other authorization site. A team-aware auth manager distinguishes a team-scoped Dag from a global one by that field -- the Keycloak auth manager, for example, checks the DAG resource instead of DAG: -- so the team-scoped permission that should gate the request was never consulted. In a deployment running multi-team mode with a team-aware auth manager, an authenticated user in one team could trigger Dag runs belonging to another team, supplying their own dag_run_id and conf, and could read another team's XCom values. Deployments using the FAB auth manager are unaffected, as it has no multi-team support. Users are advised to upgrade to apache-airflow 3.3.1 or later, which resolves the Dag's team at both sites.
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-68971 has been found in apache-airflow.
Attackers can target a specific entry point like POST /api/v2/assets/{asset_id}/materialize 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.3.1 or later.
If unsure, ask your IT team or search "apache-airflow CVE-2026-68971" on the vendor's site.
CVE-2026-68971 (apache-airflow) — CWE-862 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v2/assets/{asset_id}/materialize / wait_dag_run_until_finished / DAG / dag_run_id
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-862) exists in apache-airflow. Attackers reach the vulnerable code path via POST /api/v2/assets/{asset_id}/materialize.
Check the vendor advisory for the affected versions of apache-airflow. Attack surface: POST /api/v2/assets/{asset_id}/materialize / wait_dag_run_until_finished / DAG / dag_run_id.
Severity: Medium (CVSS 6.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 POST /api/v2/assets/{asset_id}/materialize requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/v2/assets/{asset_id}/materialize' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/v2/assets/{asset_id}/materializeへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade apache-airflow to 3.3.1ステージング環境で 3.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/v2/assets/{asset_id}/materialize on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
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