CVE-2026-96285

published 9 Nov 2026 · updated 12 Nov 2026

Apache Airflow: Scheduler: next_kwargs deserialized before the dict check, so resume data still invokes constructors

8.8HighCVSS 8.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.4.0.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Apache Software Foundation>=3.3.0 <3.4.03.4.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-96285 severity on Zeptric[![CVE-2026-96285](https://zeptric.io/badge/cve/CVE-2026-96285.svg)](https://zeptric.io/cve/CVE-2026-96285)