cve.bz

CVE-2026-33264 apache airflow: Deserialization of Untrusted Data

9.8 criticalEPSS 1.6%Fix available

Critical (9.8) in apache airflow. EPSS 1.6% estimated probability of exploitation activity in the next 30 days. Fixed in apache-airflow 3.3.0.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.6% (unchanged from 1.6% a week ago; 1.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 77th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-07-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-33264 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-33264?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-33264?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-33264 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-33264

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-33264](https://cve.bz/cve/badge/CVE-2026-33264.svg)](https://cve.bz/cve/CVE-2026-33264)

HTML:

<a href="https://cve.bz/cve/CVE-2026-33264"><img src="https://cve.bz/cve/badge/CVE-2026-33264.svg" alt="CVE-2026-33264"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Airflowbefore 3.0.0
Apache Software Foundation Apache Airflowfrom 3.0.0 before 3.3.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2943-9672-r45wPyPIapache-airflow<3.3.03.3.0
PYSEC-2026-2082PyPIapache-airflow<3.3.03.3.0

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON