GPU VulnDB

Database/Control plane, storage & DevOps

Airflow: failed token revocation at logout is ignored, so the token stays valid

UnscoredCVE-2026-113508Control plane, storage & DevOpscurated

Impact

The logout endpoint tries to revoke the presented token, ignores any failure, and still reports success. When the auth manager redirects logout to an external URL (for example the FAB or Keycloak auth managers), server-side revocation is the only thing that invalidates the Airflow token. Revocation fails on database errors, and it always fails for tokens from an external issuer accepted via [api_auth] trusted_jwks_url whose token identifier is longer than 32 characters. Anyone holding a copy of the token can keep using the Airflow API until it expires.

Who can reach it

Anyone holding a copy of a user's Airflow API token from before logout, on deployments whose auth manager uses an external logout URL.

What to do

Upgrade apache-airflow to 3.4.0 or later and restart the API server. Short token lifetimes reduce the exposure until then.

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.