# CVE-2026-65199: Huawei openUBMC low-privilege SNMP to administrator privilege escalation

> Low-privilege SNMP users can escalate to administrator privileges in Huawei openUBMC due to incorrect privilege assignment for pseudo-identities.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-246r-j53h-wrm2

## What is CVE-2026-65199?

CVE-2026-65199 is a medium-severity vulnerability in Huawei openBMC, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

openUBMC assigns the full privilege set to pseudo-identities representing SNMP callers. An authenticated, but low-privilege, SNMP user can therefore invoke mapped backend operations as an administrative identity. In `route_mapper/account.lua`, `get_user_privilege` returns the complete nine-privilege set for a `special_users` group that includes the `SNMPv1_v2c` pseudo-user.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-65199 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65199 is a medium-severity vulnerability in Huawei openBMC, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65199 in the wild and no public exploit code.

Affected product: Huawei openBMC. 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-65199/ (Markdown: https://insights.sbomify.com/CVE-2026-65199/index.md)
```

## Sources

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

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