Skip to main content
VulnerabilityPublished

CVE-2026-40913: Apache Airflow · Improper Authorization

Affects Apache AirflowSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 3.4.0 when convenient.

Data as of 9 Nov 2026, 10:47 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
Patch
Available – fixed in 3.4.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Apache Airflowapache-airflow-coreAffected
  • <3.4.0
Fixed in
  • 3.4.0
PyPIapache-airflow-corepkg:pypi/apache-airflow-coreOther threatsAffected
  • <3.4.0
Fixed in
  • 3.4.0

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 the vulnerability is fixed by restricting stack trace access to users with the new IMPORT_ERRORS_ALL permission. No other mitigation is required as the fix is official and available.

Description

Apache Airflow versions prior to 3.4.0 have an improper authorization vulnerability in the Import Errors API. The API returns raw parse-failure stack traces to any user with the ImportError.can_read permission when the failing file has no registered DAG. This can expose sensitive file paths and code to unauthorized users. The issue is fixed in Apache Airflow 3.4.0, which restricts stack trace access to users with the new IMPORT_ERRORS_ALL permission.

References

Community reviews

Loading reviews…