Deserialization of Untrusted Data Affecting airflow-2 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.68% (49th 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-AIRFLOW2-17944437
  • published11 Jul 2026
  • disclosed1 Jun 2026

Introduced: 1 Jun 2026

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

How to fix?

There is no fixed version for Minimos:latest airflow-2.

NVD Description

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

Apache Airflow's scheduler-side deadline-reference decoder (SerializedCustomReference.deserialize_reference) imported and dispatched arbitrary class paths drawn from DAG-author-controlled serialized state without an allowlist or plugin-registry gate. A DAG author whose code reaches the scheduler — the default on single-host deployments where the DAG bundle is importable from the scheduler process — could embed a custom DeadlineReference whose serialized form named an attacker-controlled module path, causing the scheduler to import_string(...) and instantiate that class with a live SQLAlchemy session attached. Affects deployments where DAG-author code is less trusted than the scheduler process. Users are advised to upgrade to apache-airflow 3.2.2 or later.