Apache Airflow's asset API endpoints returned the IDs of Dags that are scheduled on, produce, or consume an asset
Source GCVE Database
Not known to be exploited : upgrade to 3.0.0 when convenient.
Data as of 9 Nov 2026, 13:33 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.0.0, 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 9 Nov 2026.
What to do
Upgrade Apache Airflow and apache-airflow to 3.0.0; Apache Airflow and apache-airflow-core to 3.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Airflowapache-airflow | Affected
| Fixed in
|
| Apache Airflowapache-airflow-core | Affected
| Fixed in
|
PyPIapache-airflowpkg:pypi/apache-airflowOther threats | 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 check issue has been fixed. No other mitigations are indicated.
Description
Apache Airflow's asset API endpoints exposed the IDs of DAGs related to assets without verifying if the caller had permission to view those DAGs. This allowed authenticated users with asset read access to infer the existence of DAGs they were not authorized to see. Users should upgrade to Apache Airflow version 3.4.0 or later to address this issue.