CVE-2025-7043 Refresh Token Misuse via Validation Flaw in Multiple WSO2 Products Enables Unauthorized Resource Consumption
Attackers can use stolen refresh tokens to access protected resources directly, bypassing client credential validation in WSO2 products.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-7043?
CVE-2025-7043 is a medium-severity authentication bypass vulnerability in WSO2 Forgerock Key Manager Component, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-862
Which versions are affected by CVE-2025-7043?
How do I fix CVE-2025-7043?
No fix has been published for CVE-2025-7043 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2025-7043 being exploited?
There is no known exploitation of CVE-2025-7043 in the wild and no public exploit code.
Sources
Also known as GHSA-vp4v-gjpc-c4x6.