Apache Airflow: Assets events API returns asset events for every Dag with no per-Dag authorization filter
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Airflow 3.3.2, 3.0.0 and 3.3.2.
Apache Airflow's `/assets/events` API returned asset events for every Dag in the deployment, with no filter restricting them to the Dags the caller is authorized to read. Any authenticated user holding asset-read access could therefore enumerate asset events — including the source Dag ID, task ID, run ID and event timestamps — for Dags they have no permission to see. Because the filter was also absent from the count query, `total_entries` and pagination disclosed the existence of hidden Dags even without inspecting individual rows. Deployments are affected whenever per-Dag access control is used to separate teams or tenants; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Apache | Airflow | <3.3.2 | 3.3.2 |
| Apache Software Foundation | <3.0.0, >=3.0.0 <3.3.2 | 3.0.0, 3.3.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Airflow, strongest first
Embed
A live severity badge for an advisory, README or ticket