# CVE-2025-10908: Account Lock Bypass via Magic Link or Pass Key Authentication in WSO2 Identity Server Allows Unauthorized Access

> Attackers can bypass account lockouts using Magic Link or Pass Key authentication in WSO2 Identity Server, gaining unauthorized access to restricted accounts.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-rv9h-9wv4-5fxx

## What is CVE-2025-10908?

CVE-2025-10908 is a high-severity authentication bypass vulnerability in Wso2 Identity Server, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to a lack of user account state validation during authentication, locked user accounts can be successfully authenticated using Magic Link or Pass Key methods. This bypasses the intended security control that should prevent access to accounts that have been locked.

This vulnerability may allow unauthorized access to applications and sensitive data associated with accounts that should have been restricted via the account lock mechanism. It also undermines the effectiveness of the account lock mechanism intended to prevent further login attempts.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Wso2 Identity Server.

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

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

## Is CVE-2025-10908 being exploited?

There is no known exploitation of CVE-2025-10908 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-0663](https://insights.sbomify.com/CVE-2025-0663/): Auth bypass in WSO2 Identity Server (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10908 is a high-severity authentication bypass vulnerability in Wso2 Identity Server, published on 11 May 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-10908 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-10908/ (Markdown: https://insights.sbomify.com/CVE-2025-10908/index.md)
```

## Sources

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

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