# CVE-2026-81531: Unauthenticated Account Information Disclosure in Multiple Omada Controllers

> Unauthenticated attackers can query an exposed API endpoint to disclose account information, facilitating user enumeration and targeted attacks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-2pv5-9q5x-x59w

## What is CVE-2026-81531?

CVE-2026-81531 is a medium-severity vulnerability in TP Link Systems Inc. OC200 V1, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An information
disclosure vulnerability has been identified in Omada Controller.  An API endpoint intended for Controller initialization
remains accessible after completion and may disclose account-related
information to unauthenticated remote users. 

Successful
exploitation may allow an attacker to remote query the affected endpoint that
may facilitate user enumeration and subsequent attacks targeting administrative
accounts.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-81531 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81531 is a medium-severity vulnerability in TP Link Systems Inc. OC200 V1, published on 8 Sep 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-2026-81531 in the wild and no public exploit code.

Affected product: TP Link Systems Inc. OC200 V1. 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-81531/ (Markdown: https://insights.sbomify.com/CVE-2026-81531/index.md)
```

## Sources

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

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