Posted by Rahul Vats on Nov 08 Severity: moderate Affected versions: - Apache Airflow 3.0.0 before 3.4.0 Description: Apache Airflow's Task Execution API stored XCom values written by a task without the reserved-key check applied elsewhere, so a Dag author's task could write an XCom that, when a use
Briefing
Written from the coverage below · deepseek-v4.1-flash
Apache Airflow versions 3.0.0 before 3.4.0 let task-written XComs bypass the reserved-key check in the Task Execution API. When a user views such a value through the API with deserialization enabled, the API server instantiates airflow.* classes with Dag-controlled arguments.
Why it mattersAuthenticated Dag authors can abuse XCom deserialization to instantiate arbitrary airflow.* classes server-side, risking API server compromise. Upgrade Airflow.
ActionUpgrade Apache Airflow to 3.4.0 or later.
Coverage
1 article