Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45360 high CVSS 7.3

Unsafe Deserialization in apache-airflow (CVE-2026-45360)

Summary

Vulnerability in apache-airflow (CVE-2026-45360). Risk of unauthorized operations or information disclosure. Exploitable via DeadlineReference. Mitigation: upgrade to 3.2.2 or later.

Original description

The description as published by the source.

Apache Airflow's scheduler-side deadline-reference decoder (SerializedCustomReference.deserialize_reference) imported and dispatched arbitrary class paths drawn from DAG-author-controlled serialized state without an allowlist or plugin-registry gate. A DAG author whose code reaches the scheduler — the default on single-host deployments where the DAG bundle is importable from the scheduler process — could embed a custom DeadlineReference whose serialized form named an attacker-controlled module path, causing the scheduler to import_string(...) and instantiate that class with a live SQLAlchemy session attached. Affects deployments where DAG-author code is less trusted than the scheduler process. 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-45360 has been found in apache-airflow.
Attackers can target a specific entry point like DeadlineReference over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.3/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-45360" on the vendor's site.

CVE-2026-45360 (apache-airflow) — CWE-502 / CVSS v3 7.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DeadlineReference
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 DeadlineReference without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of apache-airflow. Attack surface: DeadlineReference.

🔥 Severity

Severity: High (CVSS 7.3/10). Risk of unauthorized operations or information disclosure.

🔧 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 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

  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
    Apply patch patch 
    Upgrade apache-airflow to 3.2.2

    ステージング環境で 3.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

PyPI apache-airflow
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.2"}]}]
Bitnami airflow
[{"type":"SEMVER","events":[{"introduced":"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