CyberRota Analysis
AI-GeneratedApache Airflow is vulnerable due to a flaw in the `/ui/dependencies` endpoint that allows authenticated users with read permissions to enumerate unauthorized Dag identifiers through trigger and sensor dependency entries. This issue can lead to unauthorized access to sensitive information, particularly in environments that utilize per-Dag read scoping for privacy. Organizations using Apache Airflow, especially those managing multiple teams with distinct access levels, should prioritize upgrading to version 3.3.0 or later to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
A bug in Apache Airflow's `/ui/dependencies` scheduling graph endpoint applied the caller's readable-Dag filter to the top-level serialized Dag key but still emitted referenced Dag IDs through the `dep.source` and `dep.target` fields of trigger / sensor dependency entries. An authenticated UI user with read permission on some Dags could enumerate the identifiers of other Dags they were not authorized to read by inspecting the dependency graph for trigger / sensor references. Affects deployments that rely on per-Dag read scoping to keep Dag identifiers private across teams. This is a residual gap in the fix for CVE-2026-28563, which filtered the top-level Dag key but did not propagate the filter into the trigger / sensor dep-source / dep-target fields. Users who already upgraded for CVE-2026-28563 should additionally upgrade to `apache-airflow` 3.3.0 or later to cover the residual trigger / sensor dependency leak.
Related CVEs
Other vulnerabilities affecting the same vendor(s)