Loading vulnerability…
CVE-2026-33264 is a remote code execution vulnerability in Apache Airflow affecting versions prior to 3.3.0. The flaw is in BaseSerialization.deserialize(), which allowed unrestricted import_string() of attacker-controlled class paths when the Scheduler or API Server loaded a serialized DAG. By embedding a malicious trigger into a DAG, a DAG author could cause attacker-controlled code to be imported and executed in the Scheduler or API Server process. This breaks Airflow’s intended security boundary, under which DAG-author code must not execute in those processes.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
[core] allowed_deserialization_classes configuration to a narrow allowlist to limit which classes may be deserialized. This does not replace patching, but can reduce exposure until an upgrade is completed.Patch, then assume compromise.
apache-airflow to version 3.3.0 or later, which addresses the unsafe deserialization behavior in BaseSerialization.deserialize(). Apply the vendor-provided fixes referenced in the associated Apache and GitHub advisories.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.