Authenticated DAG data disclosure via missing authorization
Published Feb 29, 2024 · Updated May 6, 2025
Missing authorization in Apache Airflow before 2.8.2 allows remote authenticated users to view restricted DAG code and import errors. The requires_access_dag decorator falls back to an any-DAG check for access_entity requests, while import-error handlers omit complete per-DAG checks. An account with access to one DAG can read source or error details belonging to DAGs outside its authorization scope through the UI or API.
Summary
What happened
Missing authorization in Apache Airflow before 2.8.2 allows remote authenticated users to view restricted DAG code and import errors. The requires_access_dag decorator falls back to an any-DAG check for access_entity requests, while import-error handlers omit complete per-DAG checks. An account with access to one DAG can read source or error details belonging to DAGs outside its authorization scope through the UI or API.
The record
- CVE
- CVE-2024-27906
- Published
- Feb 29, 2024
- Updated
- May 6, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow
- Classifications
- CWE-862, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 29, 2024CVE publishedPublication date reported by the CVE source.
- May 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.8.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo