CVE-2025-54550

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.

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.

### Withdrawn Advisory This advisory has been withdrawn because it only affects example implementations, not Airflow releases on PyPI. This link is maintained to preserve external references. ### Original Description 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.

El ejemplo example_xcom que se incluyó en la documentación de Airflow implementó un patrón inseguro de lectura de valores de xcom de una manera que podría ser explotada para permitir que un usuario de la interfaz de usuario (UI) que tuviera acceso para modificar XComs realizara la ejecución arbitraria de código en el worker. Dado que los usuarios de la interfaz de usuario (UI) ya son de alta confianza, esta es una vulnerabilidad de baja severidad. No afecta a la versión de Airflow; los example_dags no deben habilitarse en un entorno de producción; sin embargo, los usuarios que siguieron el ejemplo podrían replicar el patrón incorrecto. La documentación de Airflow 3.2.0 contiene una versión del ejemplo con resiliencia mejorada para ese caso. Se aconseja a los usuarios que siguieron ese patrón que ajusten sus implementaciones en consecuencia.