apache-airflow
Affected
- introduced
3.2.0, fixed3.2.2(ecosystem)
Fixed versions
3.2.2
Fix
- Fixed version
3.2.2pip install --upgrade apache-airflow==3.2.2
Advisory
Also known as: BIT-airflow-2026-45360, CVE-2026-45360, PYSEC-2026-186
Apache Airflow Vulnerable to Deserialization of Untrusted Data
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.
High Basis: The source's own band: HIGH
3.2.0, fixed 3.2.2 (ecosystem)3.2.2
3.2.2pip install --upgrade apache-airflow==3.2.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0