CVE-2026-40963
Airflow UI External Dependency Graph Information Disclosure
Publication date: 2026-06-01
Last updated on: 2026-06-01
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | airflow | From 3.2.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in the structure_data endpoint of the Apache Airflow UI, which returned external dependency graph nodes for linked DAGs without verifying if the user had read permission on those linked DAGs.
This means that an authenticated user who was authorized to access one DAG could enumerate the IDs and dependency metadata of other DAGs they were not authorized to read, potentially exposing private DAG dependency information.
The issue affects deployments that rely on per-DAG read scoping to keep DAG dependency topology private across teams.
The vulnerability was fixed by introducing filtering that ensures only DAGs readable by the caller are included in the response.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an authenticated user with access to one DAG to discover the existence and dependency structure of other DAGs they should not have access to.
Such unauthorized enumeration can lead to information disclosure about the workflow dependencies and topology of other teams or projects, potentially exposing sensitive operational details.
If your deployment relies on per-DAG read permissions to maintain privacy and separation between teams, this vulnerability undermines that security model.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves unauthorized enumeration of linked DAG IDs and dependency metadata via the structure_data endpoint in the Airflow UI/API by authenticated users with access to at least one DAG.
To detect this vulnerability on your system, you can attempt to access the structure_data endpoint with an authenticated user who has read permission on one DAG and check if the response includes dependency information for other DAGs that the user should not have access to.
A possible approach is to use curl or similar HTTP clients to query the structure_data endpoint and inspect the returned JSON for unauthorized DAG dependency information.
- Example command: curl -u <user>:<password> 'http://<airflow-host>/api/v1/structure_data?dag_id=<authorized_dag_id>'
- Check the response JSON for presence of linked DAG IDs that the user should not have permission to read.
What immediate steps should I take to mitigate this vulnerability?
The recommended immediate mitigation is to upgrade Apache Airflow to version 3.2.2 or later, which includes the fix that restricts the structure_data endpoint to only return dependency information for DAGs the caller is authorized to read.
Until the upgrade can be applied, consider restricting access to the Airflow UI/API to trusted users only and review DAG-level permissions to minimize exposure.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows an authenticated user with read access to one DAG to enumerate linked DAG IDs and dependency metadata for other DAGs they are not authorized to read. This could lead to unauthorized disclosure of information about the structure and existence of DAGs across teams.
Such unauthorized information disclosure may impact compliance with data protection standards and regulations like GDPR and HIPAA, which require strict access controls and protection of sensitive information. If DAG dependency topology or metadata contains sensitive or regulated information, this vulnerability could lead to non-compliance by exposing data to unauthorized users.
Users relying on per-DAG read scoping to keep DAG dependency topology private across teams are particularly affected, as the vulnerability breaks this isolation.
Upgrading to Apache Airflow version 3.2.2 or later, which includes a fix that filters out unreadable DAGs from the structure_data endpoint response, is advised to mitigate this risk and help maintain compliance.