CVE-2026-33264

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

1.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-07 10:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-11-03 07:19 UTC Last updatedMost recent change to the record

Details

Published

2026-07-07 10:16 UTC

Last modified

2026-11-03 07:19 UTC

Exploit probability

1.6% · EPSS, next 30 days

Weakness

CWE-502 · Unsafe deserialization

Record status

Analyzed

Affected

• Apache Airflow < 3.3.0

Attack profile CVSS 3.1 · 9.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High