Unsafe Deserialization in apache-airflow (CVE-2026-58076)
Summary
Vulnerability in apache-airflow (CVE-2026-58076). Successful exploitation can lead to full system takeover. Exploitable via GET /api/v2/dags/{dag_id}/details. Mitigation: upgrade to 3.3.1 or later.
Original description
The description as published by the source.
Apache Airflow's serialization layer reconstructed exception nodes by calling import_string() on a class name taken from the serialized blob and instantiating it with arguments from the same blob, with no restriction on what could be imported. An operator's executor_config reaches that branch, so a Dag author could place a value there that causes an arbitrary callable to be imported and invoked -- for example subprocess.check_output, or builtins.eval on the builtins-prefixed variant. The code runs in the Scheduler, which reconstructs serialized Dags in its normal loop with no request involved, and in the API server, on any authenticated read of the Dag such as GET /api/v2/dags/{dag_id}/details. Both are components the Airflow security model states must never execute Dag-author code, and both hold the metadata database credentials and the JWT signing secret. No non-default configuration is required. This is a different sink from CVE-2026-33264, which covered only the trigger branch of the same deserializer: deployments that upgraded in response to that advisory are still affected through the exception branch and must upgrade again. Users are advised to upgrade to apache-airflow 3.3.1 or later, which restricts the imported class to a subclass of BaseException.
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-58076 has been found in apache-airflow.
Attackers can target a specific entry point like GET /api/v2/dags/{dag_id}/details over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/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-58076" on the vendor's site.
CVE-2026-58076 (apache-airflow) — CWE-502 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v2/dags/{dag_id}/details / executor_config / subprocess.check_output / builtins.eval
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.
Unsafe deserialization (CWE-502) exists in apache-airflow. Attackers reach the vulnerable code path via GET /api/v2/dags/{dag_id}/details.
Check the vendor advisory for the affected versions of apache-airflow. Attack surface: GET /api/v2/dags/{dag_id}/details / executor_config / subprocess.check_output / builtins.eval.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
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 GET /api/v2/dags/{dag_id}/details 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 'GET /api/v2/dags/{dag_id}/details' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v2/dags/{dag_id}/detailsへの異常なリクエスト (不正な認証ヘッダ・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 GET /api/v2/dags/{dag_id}/details on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory lists.apache.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web cve.org
- web github.com
- web github.com
- web github.com
- web github.com