Apache Airflow: Event Log detail endpoint bypasses DAG-scoped event log permission filter
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Airflow 3.2.2, 3.0.0 and 3.2.2.
The Event Log detail endpoint `GET /api/v2/eventLogs/{event_log_id}` in Apache Airflow fetched audit-log rows directly by numeric ID after only the generic Audit Log permission check, while the collection endpoint `GET /api/v2/eventLogs` applied per-Dag scoping. An authenticated UI/API user with audit-log read permission for one Dag could retrieve audit-log entries for any other Dag by guessing or enumerating the numeric event log ID. Affects deployments that rely on per-Dag audit-log scoping. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Apache | Airflow | <3.2.2 | 3.2.2 |
| Apache Software Foundation | <3.0.0, >=3.0.0 <3.2.2 | 3.0.0, 3.2.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