CVE-2026-40913
Apache Airflow: Import Errors API Leaks Unauthorized DAG Stack Traces via Incomplete Per-File RBAC Enforcement
No exploitation reported by the sources we read.
- Published2026-11-09
- WeaknessCWE-285
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Apache Airflow's public Import Errors API returns the raw parse-failure stack trace to any user with the `ImportError.can_read` permission when the failing file has no registered DAG. This happens when a file fails to parse before any DAG is defined, or when all of its previously registered DAGs are removed but the parse error remains. Users who should not see that file's details can read stack traces that may expose file paths and code. Users are advised to upgrade to Apache Airflow 3.4.0 or later, which restricts these stack traces to users with the new `IMPORT_ERRORS_ALL` permission.
Timeline
dates in UTC- 2026-11-0910:00CVE publishedCNA
Versions per branch
Products declared by the CNA
As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.
- Apache Software Foundation Apache Airflowother versions: not affected
package apache-airflow-corehttps://pypi.python.org
Affected- < 3.4.0fixed in 3.4.0semver
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-09
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-40913 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-12
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-12
- CISA-ADPSSVC decisionnone2026-11-12
- CISA-ADPCVSS 3.18.22026-11-12
- CNAweakness (CWE)CWE-2852026-11-09
- FIRST EPSSEPSS score0.2 %2026-11-11
- GitHub Advisoriesadvisory—
Identifiers
- EUVD-2026-119907same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-r5cg-4fxg-38f2same flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
- Published
- 2026-11-09
- Last Modified
- 2026-11-12
- NVD status
- Awaiting Analysis
- GitHub Advisory
- GHSA-r5cg-4fxg-38f2
Frequently asked questions
What is CVE-2026-40913?
Is CVE-2026-40913 actively exploited?
What is the CVSS score for CVE-2026-40913?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-r5cg-4fxg-38f2
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OpenCVE · OpenCVE terms of service · terms restrict redistribution
- CISA Vulnrichment · CC0-1.0