CVE-2026-75158: Apache Airflow: Assets events API returns asset events for every Dag with no per-Dag authorization filter
Apache Airflow before 3.3.2 lets asset readers enumerate events for every Dag via CVE-2026-75158.
Apache Airflow before 3.3.2 has a moderate authorization flaw, CVE-2026-75158, in the /assets/events API. The endpoint returned asset events for every Dag, including source Dag ID, task ID, run ID, and timestamps, without restricting results to Dags the caller may read. Any authenticated user with asset-read access could enumerate events for unauthorized Dags. The oss-security post does not report active exploitation.
- CVE-2026-75158 is rated moderate and fixed in Airflow 3.3.2.
- The assets events API omitted a per-Dag authorization filter.
- Authenticated asset readers could see Dag, task, run IDs and timestamps.
- No exploitation in the wild is reported in the advisory.
Vulnerabilities mentionedAll →
- CVE-2026-751584.3—Missing per-Dag Authorization in Apache Airflow Assets Events API Leaks Hidden Dag Datapublished · Apache Airflow
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-75158 | Missing per-Dag Authorization in Apache Airflow Assets Events API Leaks Hidden Dag Data Apache Airflow's /assets/events REST API returned asset events for every Dag in a deployment without filtering results to the Dags the caller is authorized to read. Any authenticated user holding asset-read access could trigger the flaw simply by calling the endpoint, enumerating asset events — including source Dag ID, task ID, run ID, and timestamps — for Dags belonging to other teams or tenants. Because the authorization filter was also missing from the count query, the total_entries value and pagination alone disclosed the existence of hidden Dags even without reading individual rows. Deployments that use per-Dag access control to separate teams or tenants are affected, with no special configuration required; the issue is rated medium (CVSS 3.1: 4.3) since it requires an authenticated account and causes information disclosure only. There is no known public proof of concept and no indication of exploitation in the wild. |
Posted by Rahul Vats on Sep 21 Severity: moderate Affected versions: - Apache Airflow before 3.3.2 Description: 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...
This source does not provide full text. Read it at seclists.org.