CVE-2026-3583: Improper Token Revocation via OAuth2 Scope Enforcement in Multiple WSO2 Products [Disrupted Authentication Flows]
When the allowedscopes configuration is enabled, the OAuth2 token introspection mechanism does not immediately invalidate a token in the cache after a revocation request. This results in a scenario where an access token that was introspected immediately before a revocation request may be returned again to the client after revocation, until the relevant cache entry is cleared.
The security consequence is that a revoked access token may be re-issued to the client during the cache lifetime. While the re-issued token is not treated as valid for API authorization, affected users may be unable to obtain a new valid access token until the cache is cleared, which can disrupt authentication flows.
Affected Software
Event History
Frequently Asked Questions
Which deployments are affected?
The issue applies when the allowed_scopes configuration is enabled in the OAuth2 token introspection mechanism. The provided information does not identify specific WSO2 product versions or releases.
What conditions are required to trigger the problem?
A token must be introspected immediately before a revocation request, leaving its introspection result in cache. A subsequent request can then receive the cached token result until the relevant cache entry is cleared.
Can the re-issued revoked token be used to authorize API requests?
No. The re-issued token is not treated as valid for API authorization. The stated impact is disruption to authentication flows because affected users may be unable to obtain a new valid access token until the cache is cleared.
What can be done if an update is not immediately available?
Clear the relevant token introspection cache entry after revoking a token. This removes the cached result that can cause the revoked token to be returned again.