Skip to main content
VulnerabilityPublished

CVE-2026-111395: Apache Airflow did not reject reserved serialization keys inside a Dag run's conf

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-111395· High

Not known to be exploited : upgrade to 3.4.0 soon.

Data as of 9 Nov 2026, 13:32 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 3.4.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade Apache Airflow and apache-airflow-core to 3.4.0.

Affected software

ProductAffectedFixed in
Apache Airflowapache-airflow-coreAffected
  • >=3.2.0 <3.4.0
Fixed in
  • 3.4.0
PyPIapache-airflow-corepkg:pypi/apache-airflow-coreOther threatsAffected
  • >=3.2.0 <3.4.0
Fixed in
  • 3.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Airflow to version 3.4.0 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated.

Description

Apache Airflow versions prior to 3.4.0 did not reject reserved serialization keys inside a Dag run's configuration. This flaw allowed users authorized to trigger a Dag with a deadline alert and asynchronous callback to pass a crafted configuration that could cause the scheduler to crash repeatedly or cause improper object reconstruction inside the Triggerer after a missed deadline. Upgrading to Apache Airflow 3.4.0 or later resolves this issue.

References

Community reviews

Loading reviews…