Deserialization in Apache Airflow
CVE-2026-67587
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.
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.006, 49.9th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Apache Airflow
- Apache Software Foundation Airflow — versions 3.3.0
Weakness classification (CWE)
References
- github.com/apache/airflow/pull/70704 (Patch, patch, Issue Tracking)
- www.cve.org/CVERecord (related, Not Applicable)
- www.cve.org/CVERecord (related, Not Applicable)
- lists.apache.org/thread/o00ww4n69qojvsckb464dtwd2nhzy6t0 (vendor-advisory, Mailing List, Vendor Advisory)