openUBMC assigns the full privilege set to pseudo-identities representing SNMP callers. An...
Summary
Vulnerability reported (CVE-2026-65199). Risk of unauthorized operations or information disclosure. Exploitable via get_user_privilege.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-65199 has been found.
Attackers can target a specific entry point like get_user_privilege over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-65199" on the vendor's site.
CVE-2026-65199 — CWE-266 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: get_user_privilege / special_users / SNMPv1_v2c
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-266) has been reported. Attackers reach the vulnerable code path via get_user_privilege.
Check the vendor advisory for the affected versions. Attack surface: get_user_privilege / special_users / SNMPv1_v2c.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web runzero.com
- web github.com