In the Apache Airflow FAB auth manager, a DAG whose `dag_id` is `DAGs` collided with the global all-DAGs permission resource name produced by `resource_name()`, so a user granted per-DAG `access_control` on that one DAG was silently granted the global all-DAGs permission (privilege escalation). The escalation triggers when a DAG named `DAGs` exists and a lower-privileged user is given per-DAG access to it, granting that user read/edit access to every DAG. Users are advised to upgrade to `apache-airflow-providers-fab` 3.7.2 or later, which disambiguates the resource-name collision.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/apache/airflow/pull/69106 Issue Tracking, Patch
- https://lists.apache.org/thread/70f37q3mwov1vm3zolrfxlzds278c78h Mailing List, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.1 · apacheNVD modified 2026-10-24 22:10
Affected (CPE criteria) 1
cpe:2.3:a:apache:apache-airflow-providers-fab:*:*:*:*:*:*:*:*
References 3
- https://github.com/apache/airflow/pull/69106 Issue Tracking, Patch
- https://lists.apache.org/thread/70f37q3mwov1vm3zolrfxlzds278c78h Mailing List, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/07/13/4 Mailing List, Third Party Advisory