Posted by Rahul Vats on Nov 08 Severity: moderate Affected versions: - Apache Airflow 3.2.0 before 3.4.0 Description: Apache Airflow did not reject reserved serialization keys inside a Dag run's `conf`. A user allowed to trigger a Dag that uses a deadline alert with an asynchronous callback could pa
Briefing
Written from the coverage below · deepseek-v4.1-flash
Apache Airflow 3.2.0 through 3.4.0 did not reject reserved serialization keys in a Dag run's conf. A user who can trigger a Dag with an asynchronous deadline callback could pass a conf that, on a missed deadline, repeatedly crashed the scheduler or rebuilt objects in the Triggerer.
Why it mattersAny user able to trigger Dags can crash the scheduler repeatedly, disrupting all pipeline runs on the instance.
ActionUpgrade Apache Airflow to 3.4.0 or later.
Coverage
1 article