apache-airflow
Affected
- introduced
0, fixed3.3.2(ecosystem)
Fixed versions
3.3.2
Fix
- Fixed version
3.3.2pip install --upgrade apache-airflow==3.3.2
Advisory
Also known as: BIT-airflow-2026-75158, CVE-2026-75158
The record has no summary.
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.
Medium Basis: CVSS v3 score 4.3, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
0, fixed 3.3.2 (ecosystem)3.3.2
3.3.2pip install --upgrade apache-airflow==3.3.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0