# CVE-2025-10611: Potential Broken Access Control in Multiple WSO2 Products via System REST APIs

> Attackers can bypass authentication on WSO2 REST APIs to gain administrative access and perform unauthorized operations.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** GHSA-q35x-jjjw-76gp

## What is CVE-2025-10611?

CVE-2025-10611 is a critical missing authorization vulnerability in Wso2 Api Manager, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to an insufficient access control implementation in multiple WSO2 Products, authentication and authorization checks for certain REST APIs can be bypassed, allowing them to be invoked without proper validation.

Successful exploitation of this vulnerability could lead to a malicious actor gaining administrative access and performing unauthenticated and unauthorized administrative operations.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 9 products.


Products: Wso2 Api Control Plane, Wso2 Api Manager, Wso2 Identity Server, Wso2 Identity Server as Key Manager, Wso2 Open Banking Am, Wso2 Open Banking Iam, Wso2 Open Banking Km, Wso2 Traffic Manager, Wso2 Universal Gateway.

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

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

## Is CVE-2025-10611 being exploited?

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

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2026-5430](https://insights.sbomify.com/CVE-2026-5430/): WSO2 Multiple Products Path Traversal Vulnerability (critical 10.0, exploited in the wild)
- [CVE-2026-1728](https://insights.sbomify.com/CVE-2026-1728/): Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover (critical 9.8)
- [CVE-2025-9312](https://insights.sbomify.com/CVE-2025-9312/): Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products (critical 9.8)
- [CVE-2025-9152](https://insights.sbomify.com/CVE-2025-9152/): Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint (critical 9.8)
- [CVE-2025-9804](https://insights.sbomify.com/CVE-2025-9804/): Improper Access Control in Multiple WSO2 Products via Internal SOAP Admin Services and System REST APIs (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10611 is a critical missing authorization vulnerability in Wso2 Api Manager, published on 16 Oct 2025. 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-10611 in the wild and no public exploit code.

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

## Sources

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

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