CVE-2026-40913 · Runtime
NO FIX YET · SEE WHAT TO DO
Airflow's public Import Errors API returns the raw stack trace of a DAG file that failed to parse, to any user holding the ImportError.can_read permission, when that file has no registered DAG. An attacker with that read permission can see file paths and code from files they should not see.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running Apache Airflow 3.x with role-based access where some users hold ImportError.can_read but should not see every DAG file's details. Exposure requires a DAG file that fails to parse or whose DAGs were all removed, so the stack trace is still served. Installations where every reader can see every file, or where the permission is not granted to anyone outside operators, have little to lose.
Not affected if managed-hosting, single-user-deployment
Who cares apache-airflow, rbac, self-hosted
airflow version and compare it to the fixed range below.ImportError.can_read in the Airflow access control configuration.3.4.0 or later, which limits these stack traces to users with the new IMPORT_ERRORS_ALL permission.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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.