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

Overview

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.

Affected

• api_manager >= 3.2.0 < 3.2.0.434
• api_manager >= 3.2.1 < 3.2.1.54
• api_manager >= 4.1.0 < 4.1.0.218
• api_manager >= 4.2.0 < 4.2.0.156
• api_manager >= 4.3.0 < 4.3.0.67
• api_manager >= 4.4.0 < 4.4.0.30
• api_manager >= 4.5.0 < 4.5.0.14
• universal_gateway >= 4.5.0 < 4.5.0.14
• api_control_plane >= 4.5.0 < 4.5.0.15
• org.wso2.km.ext.forgerock:forgerock.key.manager >= 1.0.0 < 1.0.0.3
• org.wso2.km.ext.forgerock:forgerock.key.manager >= 1.0.0 < 1.0.0.4
• org.wso2.km.ext.forgerock:forgerock.key.manager >= 1.1.0 < 1.1.0.2
• org.wso2.km.ext.forgerock:forgerock.key.manager >= 1.1.5 < 1.1.5.3
• org.wso2.km.ext.forgerock:forgerock.key.manager >= 1.1.5 < 1.1.5.4

Remediation

Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4337/#solution