Authenticated DAG source disclosure via missing permission check
Published Jan 24, 2024 · Updated Jun 11, 2025
Missing authorization in Apache Airflow before 2.8.1 allows remote authenticated users to read source code for unauthorized DAGs. The GET /dagSources/{file_token} handler decodes a signed file token and returns DagCode for its path without checking access to every DAG in that file. A valid account with DAG Code read permission is required; the reported consequence is source disclosure without data modification or service interruption.
Summary
What happened
Missing authorization in Apache Airflow before 2.8.1 allows remote authenticated users to read source code for unauthorized DAGs. The GET /dagSources/{file_token} handler decodes a signed file token and returns DagCode for its path without checking access to every DAG in that file. A valid account with DAG Code read permission is required; the reported consequence is source disclosure without data modification or service interruption.
The record
- CVE
- CVE-2023-50944
- Published
- Jan 24, 2024
- Updated
- Jun 11, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow
- Classifications
- CWE-862, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2024CVE publishedPublication date reported by the CVE source.
- Jun 11, 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.1
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