CVE-2026-96285: Apache Software Foundation Apache Airflow
High severity, CVSS 8.8. EPSS: 0.6% probability of exploitation activity in the next 30 days.
Apache Airflow 3.3.1 shipped a fix for CVE-2026-67260 that checks the scheduler's decoded `next_kwargs` value is a dictionary, but performs that check only after deserializing the whole stored payload. Deserialization reconstructs nested objects of classes permitted by the deserialization allow-list — which by default includes Airflow's own classes — and runs their constructors inside the scheduler process before the check can reject the value. A Dag author, who controls a task's `next_kwargs` through the task execution API, can therefore still trigger constructor execution in the scheduler when the `awaiting_input` timeout sweep processes the task, and in the API server when the task instance is served to a worker using an older Execution API version; no non-default configuration is required. Versions before 3.3.0 are not affected. This is an incomplete fix for CVE-2026-67260: deployments that upgraded to 3.3.1 for that issue must also upgrade to apache-airflow 3.4.0 or later.
What to do
The record states a fixed version for the versions it affects. If you run one, update to it.
- Apache Software Foundation Apache Airflow, from 3.3.0, before 3.4.0: fixed in 3.4.0
Affected products
- Apache Software Foundation Apache Airflow: from 3.3.0, before 3.4.0 (fixed in 3.4.0)
Published 2026-11-09. Last modified 2026-11-12.