# CVE-2025-12627: Auth bypass in WSO2 Carbon OAuth

> Attackers can extend unauthorized access as impersonated users by exploiting improper refresh token handling in WSO2 Identity Server.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-8j24-697m-8w28

## What is CVE-2025-12627?

CVE-2025-12627 is a low-severity authentication bypass vulnerability in Wso2 Identity Server, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The user impersonation flow in WSO2 Identity Server fails to properly manage refresh tokens associated with impersonated sessions. This allows an attacker who has obtained an access token for an impersonated user to leverage the refresh token grant to obtain new access tokens, extending their ability to act as the legitimate user.

An attacker who gains access to an impersonated user's access token can exploit this weakness to renew their authorization. This results in the continued ability to perform actions on behalf of the actual user, compromising log integrity and traceability by masking the true actor.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2025-12627?

It affects 1 product.


Products: Wso2 Identity Server.

## How do I fix CVE-2025-12627?

No fix has been published for CVE-2025-12627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12627 being exploited?

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

## Other vulnerabilities in Wso2 Identity Server

- [CVE-2016-4311](https://insights.sbomify.com/CVE-2016-4311/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2025-10470](https://insights.sbomify.com/CVE-2025-10470/): Denial-of-Service via Magic Link Authentication in WSO2 Identity Server Allows Service Unavailability (high 8.6)
- [CVE-2025-12107](https://insights.sbomify.com/CVE-2025-12107/): Server-Side Template Injection via Velocity Template Engine in Multiple WSO2 Products Allows Remote Code Execution (high 8.4)
- [CVE-2016-4312](https://insights.sbomify.com/CVE-2016-4312/): XML external entity in n/a (high 7.5)
- [CVE-2025-10908](https://insights.sbomify.com/CVE-2025-10908/): Account Lock Bypass via Magic Link or Pass Key Authentication in WSO2 Identity Server Allows Unauthorized Access (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12627 is a low-severity authentication bypass vulnerability in Wso2 Identity Server, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12627 in the wild and no public exploit code.

Affected product: Wso2 Identity Server. 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-12627/ (Markdown: https://insights.sbomify.com/CVE-2025-12627/index.md)
```

## Sources

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

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