Apache Airflow’s asset queued‑events DELETE endpoints incorrectly check the caller’s Dag‑axis permission, allowing any authenticated user who possesses read access to a Dag to delete the Dag’s queued asset events. This state‑changing action silently suppresses asset‑triggered scheduling for that Dag, enabling a malicious actor to interrupt or block scheduled runs by manipulating queued events. The weakness is a read‑to‑write privilege escalation (CWE‑863).

The vulnerability affects Apache Airflow deployments that use asset‑triggered scheduling and grant Dag read access to users who do not have Dag edit rights. All versions prior to 3.3.2 are susceptible; upgrading to apache‑airflow 3.3.2 or later removes the flaw.

The flaw requires only authentication and a standard read permission, so an internal or compromised account can perform the attack. With a CVSS score of 7.5, the vulnerability is considered high severity; however, because the EPSS score is below 1% and the issue is not yet listed in CISA’s KEV catalog, exploitation likelihood remains low at present. Nevertheless, the impact on workflow availability is high, and the lack of proper authorization checks raises the overall risk.