Apache Airflow: API: asset queuedEvents DELETE checks Dag edit on a ?dag_id query value but deletes rows for every readable Dag
- 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? →
- 19/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Apache Airflow's API endpoint for deleting an asset's queued events checks edit permission only on the `dag_id` query value, but deletes queued events for every Dag the caller can read. An authenticated user with edit access to one Dag and read access to others can suppress asset-triggered runs of Dags they cannot edit. This is an incomplete fix for an earlier issue, so installations that applied that earlier fix remain affected.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Apache Airflow's API endpoint for deleting an asset's queued events checked Dag edit permission against the dag_id query parameter, but deleted the queued events of every Dag the caller could read. An authenticated user with edit permission on one Dag and read access to others could suppress asset-triggered runs of Dags they cannot edit. This is an incomplete fix for CVE-2026-75157: users who upgraded to apache-airflow 3.3.2 for that fix are still affected and should upgrade to apache-airflow 3.4.0 or later.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach12/20apache-airflow-core: 647K downloads a week
- Severity4.3/10CVSS 4.3
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 38 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
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
From 3.3.2 · 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-111453
Is CVE-2026-111453 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-111453?
apache-airflow-core (PyPI): from 3.3.2 before 3.4.0.Source: cve.now feed data
How do I fix CVE-2026-111453?
Upgrade to a fixed version: 3.4.0.Source: cve.now feed data
Why is it rated 4.3 Medium?
CVSS 4.3 scores the worst case. apache rates it Low.