GPU VulnDB

Database/Control plane, storage & DevOps

Apache Airflow: asset materialize permission lets a user trigger DAGs they have no access to

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

Impact

A UI or API user holding only the asset materialize permission can trigger DAG runs for DAGs they are not authorized to see or run. On a fleet where Airflow drives training, fine-tuning and batch inference pipelines, that means a restricted user can launch another team's jobs - consuming GPU hours, writing to datasets and model stores they do not own, and running code under the permissions of the worker that executes the DAG. The authorization check belongs to the materialize path, so the usual per-DAG access control does not contain it.

Who can reach it

Authenticated Airflow user with the asset materialize permission, over the web UI or REST API. No DAG-level access and no administrative role required.

What to do

Upgrade to Apache Airflow 3.2.0, which fixes the check, and restart the webserver/API server and scheduler - a control-plane daemon restart, no node drain and no impact on GPU nodes themselves. Until then, review who holds asset materialize and remove it from roles that should not be able to start pipelines, and audit recent DAG runs for triggers that did not come from their owning team.

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.