CVE-2026-3583
Improper Token Revocation via OAuth2 Scope Enforcement in Multiple WSO2 Products [Disrupted Authentication Flows]
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-3583 divulgada · CVSS 3.1 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación ninguna | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
The affected software is multiple WSO2 products that use OAuth2 token introspection with the allowed_scopes setting enabled. In these products, a revoked access token can be returned to clients from cache until the cache entry expires, which can prevent users from obtaining new valid tokens and disrupt their authentication.
Descripción original del registro (WSO2)
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.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
WSO2 API Manager |
Corregida | 3.1.0.367, 3.2.0.475, 3.2.1.106, 4.0.0.394, 4.1.0.267, 4.2.0.207, 4.3.0.120, 4.4.0.83, 4.5.0.67, 4.6.0.29, 4.7.0.3 | — | — |
WSO2 Traffic Manager |
Corregida | 4.5.0.65, 4.6.0.29, 4.7.0.3 | — | — |
WSO2 Universal Gateway |
Corregida | 4.5.0.67, 4.6.0.29, 4.7.0.3 | — | — |
WSO2 API Control Plane |
Corregida | 4.5.0.68, 4.6.0.30, 4.7.0.3 | — | — |
WSO2 Identity Server |
Corregida | 5.10.0.397, 5.11.0.444, 6.0.0.270, 6.1.0.269, 7.0.0.152, 7.1.0.61, 7.2.0.20, 7.3.0.1 | — | — |
WSO2 Open Banking IAM |
Corregida | 2.0.0.434 | — | — |
WSO2 Identity Server as Key Manager |
Corregida | 5.10.0.387 | — | — |
WSO2 Open Banking AM |
Corregida | 2.0.0.414 | — | — |
WSO2 Carbon OAuth |
Corregida | 6.4.2.178, 6.4.111.174, 6.4.176.38, 6.4.180.25, 6.8.0.59, 6.9.6.36, 6.11.21.118, 6.13.16.32, 6.13.19.23, 6.13.27.21, 6.13.41.9, 6.14.14.3, 7.0.26.103, 7.0.259.54, 7.0.385.15, 7.4.99.5 | — | — |
2.0.0.4142.0.0.4343.1.0.3673.2.0.4753.2.1.1064.0.0.3944.1.0.2674.2.0.2074.3.0.1204.4.0.834.5.0.654.5.0.674.5.0.684.6.0.294.6.0.304.7.0.35.10.0.3875.10.0.3975.11.0.4446.0.0.2706.1.0.2696.4.2.1786.4.111.1746.4.176.386.4.180.256.8.0.596.9.6.366.11.21.1186.13.16.326.13.19.236.13.27.216.13.41.96.14.14.37.0.0.1527.0.26.1037.0.259.547.0.385.157.1.0.617.2.0.207.3.0.17.4.99.5Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2026-5175/Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
