# CVE-2026-102298: Insufficient Authorization and User Boundary Validation in Omada Controller MSP

> Authenticated users can bypass authorization checks to enumerate users and verify credentials for other accounts in Omada Controller MSP mode.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-992g-w5j8-qhcq

## What is CVE-2026-102298?

CVE-2026-102298 is a high-severity missing authorization vulnerability in TP-Link System Inc. Omada Software Controller (Windows), published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In Omada Controller MSP mode, the user-confirmation endpoint fails to enforce the required permission check. An authenticated user can supply a caller-controlled Identifier parameter to validate credentials for another account and receive responses that distinguish nonexistent users, invalid passwords, and successful authentication. 

Successful exploitation may allow user enumeration, credential verification, and unauthorized access to MSP resources or compromise of targeted accounts.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-102298?


## How do I fix CVE-2026-102298?

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

## Is CVE-2026-102298 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102298 and fix it if it is affected.

What it is: CVE-2026-102298 is a high-severity missing authorization vulnerability in TP-Link System Inc. Omada Software Controller (Windows), published on 14 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102298 in the wild and no public exploit code.

Affected product: TP-Link System Inc. Omada Software Controller (Windows). 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-2026-102298/ (Markdown: https://insights.sbomify.com/CVE-2026-102298/index.md)
```

## Sources

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

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