A bug in Apache Airflow's auth manager logout handling left previously-issued JWT tokens valid after the user clicked logout in the UI: the logout flow for `FabAuthManager` and `KeycloakAuthManager` did not actually reach the underlying `revoke_token()` call, so the JWT remained accepted by the API server until its natural expiry. An attacker holding a previously-issued JWT for a logged-out user could continue to make authenticated API calls as that user. Affects deployments configured with `FabAuthManager` or `KeycloakAuthManager` (the bug does not affect SimpleAuthManager). This is a residual gap in the fix for CVE-2025-57735, which addressed cookie-side invalidation in PR #57992 / PR #61339 but did not cover the provider-side `revoke_token()` reachability in the FAB / Keycloak code paths. Users who already upgraded for CVE-2025-57735 should additionally upgrade to `apache-airflow` 3.2.2 or later to cover the FAB / Keycloak logout paths.
References
| Link | Resource |
|---|---|
| https://github.com/apache/airflow/pull/67289 | Issue Tracking Patch |
| https://lists.apache.org/thread/630jg4z6cjkv4m2yv2ljgmf1zhdj1vqx | Mailing List Vendor Advisory |
| https://www.cve.org/CVERecord?id=CVE-2025-57735 | Mailing List Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-06-01 09:16
Updated : 2026-07-21 19:10
NVD link : CVE-2026-48726
Mitre link : CVE-2026-48726
CVE.ORG link : CVE-2026-48726
JSON object : View
Products Affected
apache
- airflow
CWE
CWE-613
Insufficient Session Expiration
