Apache Airflow unsafe object instantiation in deadline alerts
Apache Software Foundation Apache Airflow
Apache Software Foundation Apache Airflow
| Product | Affected | Fixed in |
|---|---|---|
| Apache Software Foundation Apache Airflow |
| No fix yet |
Apache Airflow rebuilt deadline alert fields through generic deserialization, which imports and instantiates the class named in the serialized Dag, in the scheduler and API server. A Dag author could cause classes within Airflow's deserialization allow list to be constructed in those processes with arguments they control. Deployments whose Dags use deadline alerts are affected.
This is an incomplete fix of CVE-2026-45360, which only hardened the `reference` field; deployments that applied that fix remain affected through the `callback` and `interval` fields.
Users of apache-airflow are recommended to upgrade to 3.4.0 or later.
From the CVE record · apache
Apache Airflow generically deserializes deadline alert fields in the scheduler and API server. A Dag author can cause allow-listed classes to be constructed in those processes with attacker-controlled arguments when Dags use deadline alerts. The earlier fix for the reference field does not cover the callback and interval fields.
Teams running Apache Airflow versions before 3.4.0 with Dags that use deadline alerts should check their deployments.