- Exploited
- No known exploitation
- Fix
- Fixed in 3.4.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.4.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache Airflow does not reject reserved serialization keys in a Dag run's `conf`, so a user allowed to trigger a Dag that uses a deadline alert with an asynchronous callback can submit a `conf` that, once the deadline is missed, either repeatedly crashes the scheduler or is rebuilt into objects inside the Triggerer.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach12/20apache-airflow-core: 647K downloads a week
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Impact
- Widely used
apache-airflow-core has 647k weekly downloads.Source: pypistats.org
473 packages depend on apache-airflow-core.Source: deps.dev
What to do
Upgrade to a fixed version: 3.4.0.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
From 3.2.0 · fixed in 3.4.0
Fixed in 3.4.0 (released Nov 6, 2026, 3 days before disclosure).
The latest release, 3.4.0, is not affected.
Evidence 3
- Advisory
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111395
Is CVE-2026-111395 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-111395?
apache-airflow-core (PyPI): from 3.2.0 before 3.4.0.Source: cve.now feed data
How do I fix CVE-2026-111395?
Upgrade to a fixed version: 3.4.0.Source: cve.now feed data