← Back
CVE-2026-42359
high
CVSS 8.8
Unsafe Deserialization in apache-airflow (CVE-2026-42359)
Summary
vulnerability in apache-airflow (CVE-2026-42359). Successful exploitation can lead to full system takeover. Exploitable via `PATCH /api/v2/xcomEntries/{key}`. Mitigation: upgrade to `3.2.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42359** has been found in apache-airflow.
Attackers can target a specific entry point like `PATCH /api/v2/xcomEntries/{key}` 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.2.2** or later.
If unsure, ask your IT team or search "apache-airflow CVE-2026-42359" on the vendor's site.
CVE-2026-42359 (apache-airflow) — CWE-502 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /api/v2/xcomEntries/{key} / `return_value` / `FORBIDDEN_XCOM_KEYS`
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
**unsafe deserialization** (CWE-502) exists in apache-airflow. Attackers reach the vulnerable code path via `PATCH /api/v2/xcomEntries/{key}` without authentication.
📍 Affected scope
apache-airflow — . Attack surface: PATCH /api/v2/xcomEntries/{key} / `return_value` / `FORBIDDEN_XCOM_KEYS`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 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 `PATCH /api/v2/xcomEntries/{key}` 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'PATCH /api/v2/xcomEntries/{key}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `PATCH /api/v2/xcomEntries/{key}` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade apache-airflow to 3.2.2ステージング環境で 3.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against PATCH /api/v2/xcomEntries/{key} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
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"}]}]