The vulnerability arises from an unsafe code pattern in the example_xcom DAG included in Apache Airflow documentation, which reads values from XCom in a way that can be exploited by UI users with modification access to execute arbitrary code on the worker. Since UI users are already highly trusted, the severity is considered low in practice. The vulnerability does not impact official Airflow releases because example DAGs are not meant for production. The documentation for Airflow 3.2.0 contains a safer example that addresses this issue. No official patch or remediation level has been published, and no known exploits are reported in the wild.

If an attacker has UI access with permissions to modify XComs, they could leverage this vulnerability to execute arbitrary code on Airflow workers. However, because such UI users are already highly trusted, the practical impact is limited. The vulnerability does not affect production environments unless users replicate the unsafe example pattern from the documentation.

Users should avoid using the unsafe example_xcom pattern from older Airflow documentation and instead follow the improved example provided in Airflow 3.2.0 documentation. Since the example DAG is not intended for production, disabling or not enabling example DAGs in production environments effectively mitigates the risk. There is no official patch or remediation level published; users must manually adjust their implementations if they followed the vulnerable pattern.