GPU VulnDB

Database/Control plane, storage & DevOps

Apache Airflow: bulk Task Instance API authorizes the URL dag_id but acts on the body dag_id

CVSS 7.5CVE-2026-41084Control plane, storage & DevOpscurated

Impact

The bulk Task Instance endpoint checked permissions against the dag_id in the URL path while operating on the dag_id and dag_run_id taken from request-body entities. A user with edit rights on a single Dag can therefore clear, fail or otherwise mutate Task Instance state in any other Dag by keeping their own Dag in the path and naming the target in the body. On a shared GPU cluster that uses per-Dag edit scope to keep teams apart, this lets one tenant restart or kill another tenant's training and batch work, consuming their allocation and destroying run state. Integrity only - no data is read out through this path.

Who can reach it

Any authenticated UI/API user holding edit permission on at least one Dag, over the network. Affects deployments relying on per-Dag edit scope for isolation.

What to do

Upgrade to apache-airflow 3.2.2 or later and restart the API server. No configuration-only mitigation is published; until the upgrade, the only effective control is narrowing who holds Dag edit permission at all.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.