GPU VulnDB

Database/Control plane, storage & DevOps

Apache Airflow: any authenticated task instance can read or decide another task instance's HITL approvals

CVSS 8.1CVE-2026-30911Control plane, storage & DevOpscurated

Impact

The Execution API's Human-in-the-Loop endpoints in Airflow 3.1.0 through 3.1.7 do not check that the calling task instance owns the HITL record it is acting on. Any authenticated task instance can read, approve or reject HITL workflows belonging to any other task instance. On a shared Airflow instance that orchestrates fleet work - dataset builds, training job submission, model promotion - one tenant's DAG can approve another tenant's gated step, which turns a human approval gate into something any task on the cluster can flip. Confidentiality goes with it: the HITL payloads of other teams' workflows are readable.

Who can reach it

Anyone who can run a task on the Airflow deployment, i.e. anyone able to author or trigger a DAG. Authentication as a task instance is required; no operator or admin role is needed.

What to do

Upgrade to Apache Airflow 3.1.8 or later and restart the API server and schedulers. Workers pick up the change with the new image. No node reboot or fleet drain is involved; running DAGs need the usual Airflow upgrade window.

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.