Metadata disclosure via unauthenticated lineage endpoint
Published Feb 17, 2021 · Updated Feb 13, 2025
Missing authentication in Apache Airflow 2.0.0 allows remote attackers to read DAG and task lineage metadata through the Experimental API. The get_lineage route in airflow/www/api/experimental/endpoints.py omits the requires_authentication decorator before processing attacker-supplied DAG and execution-date path parameters. Exploitation requires the deprecated API to be enabled and knowledge of valid parameters; the result is limited to DAG and task metadata disclosure.
Summary
What happened
Missing authentication in Apache Airflow 2.0.0 allows remote attackers to read DAG and task lineage metadata through the Experimental API. The get_lineage route in airflow/www/api/experimental/endpoints.py omits the requires_authentication decorator before processing attacker-supplied DAG and execution-date path parameters. Exploitation requires the deprecated API to be enabled and knowledge of valid parameters; the result is limited to DAG and task metadata disclosure.
The record
- CVE
- CVE-2021-26697
- Published
- Feb 17, 2021
- Updated
- Feb 13, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow
- Classifications
- CWE-306, CWE-269, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 2021CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=Apache Airflow 2.0.0
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.
Weakness, pattern, technique
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