Unsafe Deserialization in apache-airflow (CVE-2026-67587)
Summary
Vulnerability in apache-airflow (CVE-2026-67587). Successful exploitation can lead to full system takeover. Exploitable via Callback. Mitigation: upgrade to 3.3.1 or later.
Original description
The description as published by the source.
Apache Airflow's Task SDK rebuilt a Callback object from serialized data by re-running its constructor, which imports the module named by the stored callback path. Because SyncCallback is itself an Airflow class it passes the default allowed_deserialization_classes allow-list, so tightening that setting does not help. A Dag author — who controls a task instance's next_kwargs through the task execution API — can therefore cause an arbitrary module to be imported inside the scheduler process, when the scheduler's awaiting_input timeout sweep deserializes that value. No non-default configuration is required; the sweep runs unconditionally. Versions before 3.3.0 are not affected: the class existed, but the scheduler sweep that reaches it did not. This is a separate code path from CVE-2026-58076 and CVE-2026-67260, which cover different gadgets reaching deserialization — applying either of those fixes does not address this one. Users are advised to upgrade to apache-airflow 3.3.1 or later.
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-67587 has been found in apache-airflow.
Attackers can target a specific entry point like Callback 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-67587" on the vendor's site.
CVE-2026-67587 (apache-airflow) — CWE-502 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Callback / SyncCallback / allowed_deserialization_classes / next_kwargs
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 Callback.
Check the vendor advisory for the affected versions of apache-airflow. Attack surface: Callback / SyncCallback / allowed_deserialization_classes / next_kwargs.
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 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 lists.apache.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web cve.org
- web cve.org
- web github.com
- web github.com
- web github.com
- web github.com