Executive brief
Apache Airflow is an open-source platform used to schedule and monitor complex data workflows. A security flaw in certain interface endpoints allowed users with general access to view sensitive configuration and status details for specific workflows (DAGs) they were not supposed to see. This could lead to the exposure of internal scheduling logic and operational metadata to unauthorized internal users.
Technical details
A missing authorization vulnerability exists in the Apache Airflow UI and API within the `partitioned_dag_runs` and `pending_partitioned_dag_run` endpoints. These endpoints enforced asset-level access control but failed to implement per-DAG (Directed Acyclic Graph) authorization checks. An authenticated attacker with `Asset:read` permissions could exploit this to enumerate partition run states, schedule configurations, and asset wiring for DAGs they are otherwise restricted from accessing. The fix introduces `requires_access_dag` decorators and `ReadableDagsFilterDep` to ensure proper RBAC scoping. The issue is resolved in version 3.2.2.
Affected products
- Apache Airflow >= 3.2.0, < 3.2.2
Timeline
- 2026-04-20: patched: Fix merged into main branch and assigned to 3.2.2 milestone.
- 2026-05-31: disclosed: Public disclosure on oss-security mailing list.
- 2026-06-01: advisory: GitHub Advisory and NVD entry published.