Continued API access via skipped token revocation
Published Jun 1, 2026 · Updated Jun 1, 2026
Insufficient session expiration in Apache Airflow before 3.2.2 allows remote authenticated users to retain API access after logout. The /auth/logout endpoint returns early when FabAuthManager or KeycloakAuthManager supplies a logout URL, so revoke_token() never invalidates the JWT. Possession of a previously issued token for a logged-out user is required, and accepted tokens permit authenticated API calls as that user until natural expiry.
Summary
What happened
Insufficient session expiration in Apache Airflow before 3.2.2 allows remote authenticated users to retain API access after logout. The /auth/logout endpoint returns early when FabAuthManager or KeycloakAuthManager supplies a logout URL, so revoke_token() never invalidates the JWT. Possession of a previously issued token for a logged-out user is required, and accepted tokens permit authenticated API calls as that user until natural expiry.
The record
- CVE
- CVE-2026-48726
- Published
- Jun 1, 2026
- Updated
- Jun 1, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow
- Classifications
- CWE-613, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 1, 2026CVE publishedPublication date reported by the CVE source.
- Jun 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo