Refresh Token Misuse via Validation Flaw in Multiple WSO2 Products Enables Unauthorized Resource Consumption

Summary

The ForgeRock client fails to correctly validate refresh tokens. This allows a refresh token to be treated as a valid access token, enabling its use for consuming protected resources. This bypasses the intended security control that requires valid client credentials in addition to a refresh token to obtain a new access token. An attacker who obtains a stolen or exposed refresh token can leverage this vulnerability to directly access protected resources. This is possible because the standard security flow requiring client credentials to exchange a refresh token for an access token is circumvented.

Timeline

1. Oct 19, 2026, 4:28 PM UTCCVE published
2. Oct 28, 2026, 5:47 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Oct 28, 2026, 8:05 PM UTCRecord last updated

Affected versions

• WSO2 WSO2 API Manager

  From 3.2.0 · fixed in 3.2.0.434; From 3.2.1 · fixed in 3.2.1.54; From 4.1.0 · fixed in 4.1.0.218; From 4.2.0 · fixed in 4.2.0.156; From 4.3.0 · fixed in 4.3.0.67; From 4.4.0 · fixed in 4.4.0.30; From 4.5.0 · fixed in 4.5.0.14

• WSO2 WSO2 Universal Gateway

  From 4.5.0 · fixed in 4.5.0.14

• WSO2 WSO2 API Control Plane

  From 4.5.0 · fixed in 4.5.0.15

• org.wso2.km.ext.forgerock:forgerock.key.manager

  From 1.0.0 · fixed in 1.0.0.3; From 1.0.0 · fixed in 1.0.0.4; From 1.1.0 · fixed in 1.1.0.2; From 1.1.5 · fixed in 1.1.5.3; From 1.1.5 · fixed in 1.1.5.4

References 1