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.
Published: 2026-10-19
Score: 5.4 Medium
EPSS: n/a
KEV: No
Impact: Unauthorized Resource Consumption via Refresh Token Misuse
Action: Immediate Patch
AI Analysis

Impact

The vulnerability lies in insufficient validation of refresh tokens, allowing an attacker to treat a refresh token as a valid access token. This bypasses the security control that normally requires both a valid client credential and a refresh token to obtain a new access token. As a result, any user or attacker who possesses a stolen or exposed refresh token can directly access protected resources without playing the standard OAuth exchange flow. The weakness is formally identified as CWE-862, indicating improper authorization.

Affected Systems

WSO2 Forgerock Key Manager Component, WSO2 API Control Plane, WSO2 API Manager, and WSO2 Universal Gateway are affected. Version information is not specified in the CNA data; all current releases of these products are implicitly vulnerable until patches are applied.

Risk and Exploitability

The CVSS score of 5.4 indicates moderate severity, but the impact can be significant for services that rely on strict token validation. EPSS is not provided, so current exploitation probability is unknown, and the vulnerability is not listed in the CISA KEV catalog. Externally exposed services that accept refresh tokens represent the likely attack surface; an attacker who obtains a valid token—through phishing, credential compromise, or a client-side leak—can misuse it to consume resources. The attack vector therefore appears to be remote, dependent on token possession rather than infrastructure compromise.

Generated by OpenCVE AI on October 19, 2026 at 17:24 UTC.

Remediation

Vendor Solution

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


OpenCVE Recommended Actions

  • Apply the vendor patch or update described at https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4337/#solution
  • Verify that all client applications enforce the required client credentials before exchanging a refresh token for an access token, and disallow any direct use of refresh tokens as access tokens
  • Rotate all refresh tokens that may have been exposed and implement stricter token storage and revocation policies to minimize the risk of token theft

Generated by OpenCVE AI on October 19, 2026 at 17:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
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.
Title Refresh Token Misuse via Validation Flaw in Multiple WSO2 Products Enables Unauthorized Resource Consumption
First Time appeared Wso2
Wso2 forgerock Key Manager Component
Wso2 wso2 Api Control Plane
Wso2 wso2 Api Manager
Wso2 wso2 Universal Gateway
Weaknesses CWE-862
CPEs cpe:2.3:a:wso2:forgerock_key_manager_component:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_api_control_plane:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_api_manager:*:*:*:*:*:*:*:*
cpe:2.3:a:wso2:wso2_universal_gateway:*:*:*:*:*:*:*:*
Vendors & Products Wso2
Wso2 forgerock Key Manager Component
Wso2 wso2 Api Control Plane
Wso2 wso2 Api Manager
Wso2 wso2 Universal Gateway
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N'}


Subscriptions

Wso2 Forgerock Key Manager Component Wso2 Api Control Plane Wso2 Api Manager Wso2 Universal Gateway
cve-icon MITRE

Status: PUBLISHED

Assigner: WSO2

Published:

Updated: 2026-10-19T16:28:15.063Z

Reserved: 2025-07-03T08:50:01.588Z

Link: CVE-2025-7043

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-19T17:16:59.993

Modified: 2026-10-19T17:16:59.993

Link: CVE-2025-7043

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T17:30:13Z

Weaknesses