GPU VulnDB

Database/Control plane, storage & DevOps

Airflow AWS auth manager: SAML login CSRF silently signs a victim into the attacker's Airflow account

CVSS 8.8CVE-2026-86467Control plane, storage & DevOpscurated

Impact

The AWS auth manager's SAML flow discards the AuthnRequest ID and never checks InResponseTo, so an unauthenticated attacker who can get an operator to load a page completes a SAML login in that operator's browser using the attacker's own assertion. The operator ends up working inside a session the attacker controls, without noticing the switch. On a GPU fleet Airflow is usually the thing that holds pipeline definitions and the connections to data stores, registries and cluster credentials, so anything the operator then creates, edits or triggers - including secrets pasted into a Connection - lands where the attacker can read it. Same login-CSRF class as CVE-2026-40948 in the Keycloak auth manager.

Who can reach it

Remote and unauthenticated against the attacker's side; requires an Airflow user to visit an attacker-controlled page while able to reach the Airflow web UI. Only deployments using the AWS auth manager with SAML authentication are affected.

What to do

Upgrade apache-airflow-providers-amazon to 9.38.0 and restart the Airflow webserver/API server - provider package upgrade and daemon restart, no cluster downtime. If you run the AWS auth manager without SAML you are not affected; check whether the Keycloak auth manager fix (CVE-2026-40948) also applies to your deployment.

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.