CVE-2026-75157: Apache Airflow: Asset queued-events DELETE endpoints gated on Dag READ instead of Dag EDIT (asset-triggered scheduling suppression)
Apache Airflow's asset queued-events DELETE endpoints checked the caller's Dag-axis permission with READ instead of EDIT. Any authenticated user who could read a Dag could therefore delete that Dag's queued asset events, silently suppressing asset-triggered scheduling for it — a state-changing action gated on a read-only permission. Deployments are affected whenever asset-triggered scheduling is in use and Dag read access is granted more widely than Dag edit access, which is the normal RBAC arrangement; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Airflowto a version that resolves this vulnerability.Fixed in 3.3.2
Event History
Frequently Asked Questions
Who can exploit this issue?
Any authenticated user with READ access to a DAG can delete that DAG's queued asset events, even without EDIT access. This is most relevant where DAG read access is broader than DAG edit access, which is the normal RBAC arrangement.
When is a deployment affected?
A deployment is affected when it uses asset-triggered scheduling and grants DAG READ permission more broadly than DAG EDIT permission. No special configuration is required beyond using asset-triggered scheduling.
What is the operational impact of exploitation?
An unauthorized user can delete queued asset events for a DAG, silently suppressing asset-triggered scheduling for that DAG. The issue permits a state-changing action through a read-only permission.
What version resolves the issue?
Upgrade Apache Airflow to version 3.3.2 or later.