CVE-2026-3583
When the `allowed_scopes` 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.
- Score
- CVSS 3.1 3.1 Low
- Status
- Received - ed10eef1-636d-4fbe-9993-6890dfa878f8
- Published
- 2026-10-28
- Last modified
- 2026-10-28
- Weaknesses
- CWE-613
Affected products
- Wso2 Api Control Plane (Wso2)
- Wso2 Api Manager (Wso2)
- Wso2 Carbon Oauth (Wso2)
- Wso2 Identity Server (Wso2)
- Wso2 Identity Server As Key Manager (Wso2)
- Wso2 Open Banking Am (Wso2)
- Wso2 Open Banking Iam (Wso2)
- Wso2 Traffic Manager (Wso2)
- Wso2 Universal Gateway (Wso2)
References
- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5175/
