Live › vulnerability › CVE-2025-54550
The withdrawn advisory says the example_xcom DAG in Airflow documentation read XCom values unsafely, so a UI user who could modify XComs could run arbitrary code on the worker. The advisory states the Airflow release itself is not affected, only code copied from the example.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 17:41 UTC, 0h before NVD. All times on this page are UTC.
Only teams that copied the example_xcom DAG pattern from the Airflow documentation into their own workflows. The advisory says the Airflow release is not affected and example DAGs should not be enabled in production, so most deployments can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| apache-airflow | pypi | < 3.2.0 | 3.2.0 |
| apache airflow | vendor | < 3.2.0 | 3.2.0 |
example_xcom or copies of its pattern exist in your DAG folder.3.2.0 per the affected range; the sources say the documentation example was improved in 3.2.0.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
This advisory has been withdrawn because it only affects example implementations, not Airflow releases on PyPI. This link is maintained to preserve external references.
The example example_xcom that was included in airflow documentation implemented unsafe pattern of reading value from xcom in the way that could be exploited to allow UI user who had access to modify XComs to perform arbitrary execution of code on the worker. Since the UI users are already highly trusted, this is a Low severity vulnerability.
It does not affect Airflow release - example_dags are not supposed to be enabled in production environment, however users following the example could replicate the bad pattern. Documentation of Airflow 3.2.0 contains version of the example with improved resiliance for that case.
Users who followed that pattern are advised to adjust their implementations accordingly.
This page as .md · .json · in your agent: get_signal("CVE-2025-54550")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.