Apache Airflow: Asset queued-events DELETE endpoints gated on Dag READ instead of Dag EDIT (asset-triggered scheduling suppression)
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 7.5epss 0.4%
from disclosure to weapon1 days
Published on NVDSep 18
1st PoC+1d
exploitation probability
0.4%top 65% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Affected products
Apache Software Foundation · Apache Airflowpublic PoCs found — 1
githubgithub.com/licitrasimone/cve-2026-75157-poc★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.