Skip to main content
VulnerabilityPublished Updated

CVE-2026-33264: Apache Airflow · Deserialization of Untrusted Data

Affects Apache AirflowSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.0.0 as a priority.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.19.8
EPSS
1.6% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.0, 3.3.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade Apache Airflow and apache-airflow to 3.0.0; Apache Airflow and apache-airflow and apache-airflow-core to 3.3.0.

Affected software

ProductAffectedFixed in
Apache Airflowapache-airflowAffected
  • <3.0.0
Fixed in
  • 3.0.0
Apache Airflowapache-airflow-coreAffected
  • >=3.0.0 <3.3.0
Fixed in
  • 3.3.0
PyPIapache-airflowpkg:pypi/apache-airflowOther threatsAffected
  • <3.3.0
Fixed in
  • 3.3.0
PyPIapache-airflowpkg:pypi/apache-airflowOther threatsAffected
  • <3.0.0
Fixed in
  • 3.0.0
PyPIapache-airflow-corepkg:pypi/apache-airflow-coreOther threatsAffected
  • >=3.0.0 <3.3.0
Fixed in
  • 3.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available by upgrading Apache Airflow to version 3.3.0 or later. Additionally, deployments where DAG-author trust is limited should configure the [core] allowed_deserialization_classes setting to a narrow allowlist to restrict deserialization to safe classes.

Description

A bug in `BaseSerialization.deserialize()` allowed unrestricted `import_string()` of attacker-controlled class paths when the Scheduler / API Server loaded a serialized DAG: a DAG author could embed a malicious trigger into a DAG to gain remote code execution on the API Server / Scheduler process, crossing the Airflow security boundary that DAG-author code must never execute in those processes. Users are advised to upgrade to `apache-airflow` 3.3.0 or later. As a defense-in-depth mitigation, deployments where DAG-author trust is limited can restrict the `[core] allowed_deserialization_classes` config to a narrow allowlist.

References

Community reviews

Loading reviews…