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 enforce the wrong authorization check, requiring only Dag-level READ permission where Dag-level EDIT permission is required (CWE-863). Any authenticated user who can read a Dag, even without edit rights, can call these endpoints and delete that Dag's queued asset events. Doing so silently suppresses asset-triggered scheduling for the Dag, a state-changing action that can halt intended pipeline triggers without an obvious error. Any deployment is affected where asset-triggered scheduling is in use and Dag read access is granted more widely than Dag edit access, which is the normal RBAC arrangement and requires no special configuration. No public proof-of-concept or in-the-wild exploitation is known, the issue is not in CISA KEV, and the fix is in apache-airflow 3.3.2 and later.

Do: Upgrade to apache-airflow 3.3.2 or later. Until then, tighten RBAC so Dag READ is only granted to users who may also implicitly affect the Dag's scheduling, and audit logs for DELETE requests to the asset queued-events endpoints. Check the queued asset events for Dags readable by broad roles for signs of unexpected deletions that would have suppressed asset-triggered runs.