APACHE-AIRFLOW · CVE-2026-111395 · Runtime
NO FIX YET · SEE WHAT TO DO
Apache Airflow did not reject reserved serialization keys in a Dag run's conf. A user who can trigger a Dag with a deadline alert using an asynchronous callback can make the scheduler crash repeatedly or have objects rebuilt inside the Triggerer once the deadline is missed.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running Apache Airflow 3.x where Dags use deadline alerts with asynchronous callbacks and where some users can trigger Dag runs with a custom conf. The exposure comes from the Dag run conf path into the scheduler and Triggerer, so installations without such Dags or without untrusted triggerers are less exposed. Teams that do not use deadline alerts with async callbacks can skip it, though upgrading remains the advised step.
Not affected if no-deadline-alerts-async-callbacks, only-trusted-dag-triggerers
Who cares apache-airflow, python, scheduler, triggerer
airflow version or pip show apache-airflow; versions before 3.4.0 are affected.conf.apache-airflow or laterApache 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 pass a conf that, once the deadline was missed, either crashed the scheduler repeatedly or was rebuilt into objects inside the Triggerer. Users are advised to upgrade to apache-airflow 3.4.0 or later.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
3.4.0