The Airflow UI endpoint /ui/partitioned_dag_runs only checks asset‑level permissions, neglecting per‑Dag RBAC. An authenticated user granted the global Asset:read permission can query and retrieve state, schedule configuration, and wiring for any DAG, even if they have no explicit read rights on that DAG. This authorizes a confidential data exposure, allowing enumeration of DAG contents and execution context.

This issue affects users of Apache Airflow supplied by The Apache Software Foundation. Deployments running any Airflow version older than 3.2.2 are vulnerable, as the patch to enforce per‑Dag RBAC was released in 3.2.2.

The vulnerability exists in the UI layer and can be exercised simply by sending HTTP requests to the /ui/partitioned_dag_runs endpoint. No elevated privileges beyond a legitimate Asset:read role are required, and no additional code execution is involved. EPSS information is not available, and the vulnerability is not catalogued in CISA KEV, but the potential for unauthorized data disclosure makes the risk high for environments where sensitive DAG information is bound to strict access controls.