Deserialization of Untrusted Data Affecting airflow-3 package, versions <3.3.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
1.03% (62nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-AIRFLOW3-19634069
  • published6 Sept 2026
  • disclosed7 Jul 2026

Introduced: 7 Jul 2026

CVE-2026-33264  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

Upgrade Minimos:latest airflow-3 to version 3.3.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream airflow-3 package and not the airflow-3 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.