Apache Airflow FAB provider: a DAG named 'DAGs' collides with the global all-DAGs permission and escalates privileges

Impact

resource_name() produces the same resource name for a DAG whose dag_id is literally 'DAGs' as it does for the global all-DAGs permission. Granting a low-privileged user per-DAG access_control on that one DAG therefore silently grants them read and edit on every DAG in the deployment. In a shared Airflow that fronts a GPU fleet, per-DAG access control is exactly the boundary between teams; this collapses it, letting a user read other teams' pipeline definitions and connections and edit or trigger their jobs. The trigger is a naming coincidence, so the escalation can exist without anyone having done anything suspicious.

Who can reach it

Network, authenticated - any Airflow user who has been granted per-DAG access to a DAG named 'DAGs' via the FAB auth manager. Exploitation requires no special tooling; the user simply has permissions they should not have.

What to do

Upgrade apache-airflow-providers-fab to 3.7.2 or later, which disambiguates the resource-name collision, then restart the webserver/API server and scheduler. As an immediate check, look for a DAG whose dag_id is 'DAGs' and rename it or remove the per-DAG grants pointing at it; that removes the escalation without an upgrade. Audit which users held that grant and what they could reach.

References

Related entries

• Linux MACsec (replay protection at XPN lower-PN wrap): MACsec replay protection fails at the extended-packet-numberCVE-2026-63925 · Linux MACsec (replay protection at XPN lower-PN wrap)High
• Atlantis: workspace names escape the working directory into os.RemoveAll and os.MkdirAllCVE-2026-64679 · Atlantis (workspace path handling in atlantis.yaml and /api/plan)High
• Dell PowerStore T SDNAS: unauthenticated NFS/RPC buffer overflow allows command execution on the arrayCVE-2026-70415 · Dell PowerStore T SDNAS (NFS/RPC service)High
• Jenkins: inconsistent case handling in user and group names allows impersonation of other accountsCVE-2026-70429 · Jenkins core (user and group name case-sensitivity handling)High
• Ansible community.general: memcached fact cache unpickles values, giving code execution on the controllerCVE-2026-87874 · Ansible community.general collection (memcached fact cache plugin)High
• GlusterFS (glusterd, auth.allow): The auth.allow option does not actually restrict who may connect, so anyCVE-2018-1112 · GlusterFS (glusterd, auth.allow)High