CVE-2026-96285: Apache Airflow · Deserialization of Untrusted Data
Affects Apache AirflowSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited : upgrade to 3.4.0 soon.
Data as of 9 Nov 2026, 10:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.4.0
Exploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade Apache Airflow and apache-airflow-core to 3.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Airflowapache-airflow-core | Affected
| Fixed in
|
PyPIapache-airflow-corepkg:pypi/apache-airflow-coreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache Airflow to version 3.4.0 or later to fully remediate this vulnerability. Systems upgraded only to 3.3.1 remain vulnerable due to the incomplete fix. No other configuration changes are required to mitigate this issue.
Description
CVE-2026-96285 is a deserialization vulnerability in Apache Airflow versions 3.3.0 up to but not including 3.4.0. It arises because the scheduler deserializes stored payloads before validating that the decoded data is a dictionary, allowing execution of constructors of nested objects during deserialization. This can be triggered by a DAG author controlling task parameters via the task execution API without requiring non-default configuration. The issue is an incomplete fix of a previous vulnerability (CVE-2026-67260) fixed in 3.3.1, and full remediation requires upgrading to Apache Airflow 3.4.0 or later.