Deserialization of Untrusted Data Affecting airflow-core-2 package, versions <2.11.2-r7
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
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-CHAINGUARDLATEST-AIRFLOWCORE2-19511178
- published3 Sept 2026
- disclosed1 Jun 2026
Introduced: 1 Jun 2026
CVE-2026-45360 (opens in a new tab)How to fix?
Upgrade Chainguard airflow-core-2 to version 2.11.2-r7 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream airflow-core-2 package and not the airflow-core-2 package as distributed by Chainguard.
See How to fix? for Chainguard 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.