- 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? →
- 13/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
Summary
Apache Airflow's Import Errors API can reveal the raw stack trace of a DAG file that fails to parse to users who hold the `ImportError.can_read` permission but should not see that file, potentially exposing file paths and code. This occurs when the failing file has no registered DAG, such as when it fails before any DAG is defined or after its earlier DAGs are removed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
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
- Severity1/10Rated low by apache
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 35 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
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-40913
Is CVE-2026-40913 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-40913?
apache-airflow-core (PyPI): before 3.4.0.Source: cve.now feed data
How do I fix CVE-2026-40913?
Upgrade to a fixed version: 3.4.0.Source: cve.now feed data