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.
CVE-2026-33264
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- —
- EPSS
- 74.0%
- KEV
- Not listed
Published
July 7, 2026
Last Modified
July 8, 2026
Advisory Details (4)
Auto-updated Jul 19, 2026oss-security - CVE-2026-33264: Apache Airflow: DAG author RCE on webserver via unrestricted import_string() in BaseSerialization.deserialize()
http://www.openwall.com/lists/oss-security/2026/07/07/1Remove dead AIP-44 trigger-over-BaseSerialization path (DAT.BASE_TRIGGER)
Fix merged in apache/airflow PR #68528 on 2026-06-17 — awaiting tagged release
https://github.com/apache/airflow/pull/68528Do not deserialize trigger_kwargs when loading serialized DAGs
Fix merged in apache/airflow PR #66002 on 2026-05-07 — awaiting tagged release
https://github.com/apache/airflow/pull/66002Vendor Advisories for CVE-2026-33264(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| apache-airflow | 1.10.0 ... 3.3.0rc2 (294 versions) | 3.3.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 65× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 03:54 UTCGHSA enrichment
- 2026-07-16 23:43 UTCGHSA enrichment
- 2026-07-16 19:33 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 14:55 UTCGHSA enrichment
- 2026-07-16 10:45 UTCGHSA enrichment
- 2026-07-16 06:25 UTCGHSA enrichment
- 2026-07-16 02:13 UTCGHSA enrichment
- 2026-07-15 22:02 UTCGHSA enrichment
- 2026-07-15 17:49 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 13:35 UTCGHSA enrichment
- 2026-07-15 09:21 UTCGHSA enrichment
- 2026-07-15 05:10 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 00:59 UTCGHSA enrichment
- 2026-07-14 20:48 UTCGHSA enrichment
Show 40 moreShow fewer
- 2026-07-14 16:37 UTCGHSA enrichment
- 2026-07-14 12:26 UTCGHSA enrichment
- 2026-07-14 08:16 UTCGHSA enrichment
- 2026-07-14 04:03 UTCGHSA enrichment
- 2026-07-13 23:51 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 19:41 UTCGHSA enrichment
- 2026-07-13 15:30 UTCGHSA enrichment
- 2026-07-13 11:18 UTCGHSA enrichment
- 2026-07-13 07:08 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 02:56 UTCGHSA enrichment
- 2026-07-12 22:45 UTCGHSA enrichment
- 2026-07-12 18:34 UTCGHSA enrichment
- 2026-07-12 14:22 UTCGHSA enrichment
- 2026-07-12 10:11 UTCGHSA enrichment
- 2026-07-12 06:00 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 01:49 UTCGHSA enrichment
- 2026-07-11 21:39 UTCGHSA enrichment
- 2026-07-11 17:28 UTCGHSA enrichment
- 2026-07-11 13:18 UTCGHSA enrichment
- 2026-07-11 09:07 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 04:56 UTCGHSA enrichment
- 2026-07-11 00:45 UTCGHSA enrichment
- 2026-07-10 20:34 UTCGHSA enrichment
- 2026-07-10 16:23 UTCGHSA enrichment
- 2026-07-10 12:13 UTCEG score recompute▲ 9.80
- 2026-07-10 12:12 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 15:51 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-07-07 14:17 UTCNVD update
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:06 UTCMITRE cvelistV5
- 2026-07-07 11:56 UTCNVD update
- 2026-07-07 10:06 UTCEG score recompute
- 2026-07-07 10:06 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-20208EG 9.8CRITICAL
- CVE-2017-20207EG 9.8CRITICAL
- CVE-2017-20206EG 9.8CRITICAL
- CVE-2017-20189EG 9.8CRITICAL
- CVE-2017-10992EG 9.8EPSS 95%CRITICAL
- CVE-2013-4521EG 9.8EPSS 90%CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS 98%CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-18605EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-33264?
When was CVE-2026-33264 disclosed?
Is CVE-2026-33264 actively exploited?
What is the CVSS score of CVE-2026-33264?
How do I remediate CVE-2026-33264?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33264
Is Your Infrastructure Affected by CVE-2026-33264?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.