# 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.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-vp4v-gjpc-c4x6

## 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 (Missing Authorization)

## 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.

## Is CVE-2025-7043 being exploited?

There is no known exploitation of CVE-2025-7043 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7043 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2025-7043 in the wild and no public exploit code.

Affected product: WSO2 Forgerock Key Manager Component. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7043/ (Markdown: https://insights.sbomify.com/CVE-2025-7043/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7043
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7043
- OSV: https://osv.dev/vulnerability/CVE-2025-7043

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7043/
Summaries are generated and may contain mistakes; the official description above is the record.