Categories
CVE-2026-41084 high CVSS 7.5

Vulnerability in apache-airflow (CVE-2026-41084)

Summary

Vulnerability in apache-airflow (CVE-2026-41084). Data can be tampered with by attackers. Exploitable via DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances. Mitigation: upgrade to 3.2.2 or later.

Original description

The description as published by the source.

A bug in Apache Airflow's bulk Task Instances API (PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances) evaluated authorization against the dag_id resolved from the URL path while operating on the dag_id / dag_run_id extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag's ID in the URL path and naming the target Dag's IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to apache-airflow 3.2.2 or later.

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-41084 has been found in apache-airflow.
Attackers can target a specific entry point like DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.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-41084" on the vendor's site.

CVE-2026-41084 (apache-airflow) — CWE-639 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances / dag_id / dag_run_id
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.

❓ What is the problem

A vulnerability (CWE-639) exists in apache-airflow. Attackers reach the vulnerable code path via DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of apache-airflow. Attack surface: DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances / dag_id / dag_run_id.

🔥 Severity

Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 3.2.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances 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

  1. 1
    Identify exposure identify
    grep -r 'apache-airflow' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で apache-airflow を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade apache-airflow to 3.2.2

    ステージング環境で 3.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI apache-airflow
[{"type":"ECOSYSTEM","events":[{"introduced":"3.2.0"},{"fixed":"3.2.2"}]}]
Bitnami airflow
[{"type":"SEMVER","events":[{"introduced":"3.2.0"},{"fixed":"3.2.2"}]}]
pip apache-airflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details