Description
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:NWeakness enumeration
Affected software
Source: the vendor's advisory (CNA). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| WSO2 | WSO2 API Manager | >= 3.2.0, < 3.2.0.434; >= 3.2.1, < 3.2.1.54; >= 4.1.0, < 4.1.0.218; >= 4.2.0, < 4.2.0.156; >= 4.3.0, < 4.3.0.67; >= 4.4.0, < 4.4.0.30; >= 4.5.0, < 4.5.0.14 |
| WSO2 | WSO2 Universal Gateway | >= 4.5.0, < 4.5.0.14 |
| WSO2 | WSO2 API Control Plane | >= 4.5.0, < 4.5.0.15 |
| WSO2 | Forgerock Key Manager Component | >= 1.0.0, < 1.0.0.3; >= 1.0.0, < 1.0.0.4; >= 1.1.0, < 1.1.0.2; >= 1.1.5, < 1.1.5.3; >= 1.1.5, < 1.1.5.4 |
References
Timeline
- Published
- Oct 19, 2026
- Last modified
- Nov 4, 2026
- NVD status
- Awaiting Analysis