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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 5
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-28 20:05
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-28 20:17
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-19 16:28
- StatusReceived → Awaiting AnalysisNVD modified 2026-10-19 21:06
- First seenCVSS 5.4NVD modified 2026-10-19 17:16
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.