CVE-2026-111453: Apache Airflow · Incorrect Authorization
Affects Apache AirflowSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited : upgrade to 3.4.0 soon.
Data as of 9 Nov 2026, 09:34 UTC
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
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 8 Nov 2026.
What to do
Upgrade Apache Airflow and apache-airflow-core to 3.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Airflowapache-airflow-core | Affected
| Fixed in
|
PyPIapache-airflow-corepkg:pypi/apache-airflow-coreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache Airflow to version 3.4.0 or later, where this authorization flaw has been fixed. Users who upgraded only to 3.3.2 for the previous related fix remain vulnerable and must update to 3.4.0 or beyond. No other mitigation is indicated.
Description
Apache Airflow contains an authorization flaw in its API endpoint for deleting queued events of assets. The endpoint incorrectly checks edit permission only against the specified dag_id but deletes queued events for all Dags the user can read. This allows an authenticated user with edit permission on one Dag and read access to others to suppress runs of Dags they cannot edit. This vulnerability affects Apache Airflow versions 3.3.2 up to but not including 3.4.0. The issue was fixed in version 3.4.0.