Home

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.

PUBLISHED Reserved 2026-05-26 | Published 2026-07-07 | Updated 2026-07-07 | Assigner apache

Problem types

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Product status

Default status
unaffected

Any version before 3.3.0
affected

Credits

Mitchell Benjamin / Revamp Studio finder

Jarek Potiuk remediation developer

References

github.com/apache/airflow/pull/67627 patch

www.cve.org/CVERecord?id=CVE-2026-28563 related

lists.apache.org/thread/wzc8nflg94rq6w8f5tvtlo0o3g4wjrfl vendor-advisory

cve.org (CVE-2026-48891)

nvd.nist.gov (CVE-2026-48891)

Download JSON