Apache Airflow Import Errors API leaks stack traces (CVE-2026-40913)
The Import Errors API exposes raw parse-failure stack traces to users with ImportError.can_read permission in Apache Airflow before 3.4.0.
30
CVE-2026-40913
Apache Airflow Import Errors API Leaks Unauthorized DAG Stack Traces
- CVSS
- —
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
Apache Airflow's public Import Errors 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 leaks file paths and code to users who should not see that file's details. Affected users include those managing DAGs with unauthorized parse errors.
What to do: Upgrade to Apache Airflow 3.4.0 or later to restrict stack traces using the IMPORT_ERRORS_ALL permission.
| Product | Affected | Fixed in |
|---|---|---|
| Apache Airflow | all versions prior to 3.4.0 | 3.4.0 |
Estimated exposure
moderateNo basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
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.
- Weakness
- CWE-285