Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege SNMP credentials
-
DeliverySend SNMP request mapped to backend operation
-
ExploitPseudo-user granted full nine-privilege set in account.lua
-
ExecutionOperation executes as administrative identity
-
ImpactModify BMC configuration or privileged state
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
|
| Exploitation Conditions | Requires the attacker to already possess valid low-privilege SNMP access (an SNMPv1/v2c community string or SNMP user) to an openUBMC baseboard management controller whose SNMP interface is enabled and network-reachable. The specific precondition is openUBMC's privilege mapping in route_mapper/account.lua, where the SNMPv1_v2c pseudo-user belongs to the special_users group that get_user_privilege grants all nine privileges. Limiting factors: exploitation is bounded to operations actually exposed through the SNMP-to-backend route mapping, and it is not possible without at least low-privilege SNMP authentication (PR:L), so fully anonymous/unauthenticated exploitation is not supported by the available data. |
| Impact | This is a medium-severity privilege escalation (CWE-266, Incorrect Privilege Assignment), not a critical priority. The provided CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L, base 5.4) indicates a network-reachable, low-complexity flaw that nonetheless REQUIRES authentication (PR:L) - an attacker must already hold low-privilege SNMP access. No EPSS probability, CISA KEV listing, or POC indicator was supplied in the input, so exploitation likelihood cannot be quantified and there is no public exploit identified at time of analysis; the absence of these signals, combined with PR:L, points away from mass/automated exploitation. One internal tension to verify: the description says the SNMP pseudo-user is granted the COMPLETE nine-privilege (administrative) set, which sounds more impactful than the vector's I:L/A:L and C:N - if mapped backend operations expose sensitive reads or destructive writes, real impact may exceed the stated 5.4, so confirm the actual scope of SNMP-mapped operations with the vendor. Overall: a legitimate authenticated-insider / credential-theft escalation risk on affected BMCs, but not a drop-everything internet-wide emergency. |
| Exploit ScenarioDerived | An attacker holding a low-privilege SNMPv1/v2c community string (or SNMP user) on an openUBMC-managed baseboard management controller issues SNMP requests that are mapped to backend operations. Because get_user_privilege assigns the full administrative privilege set to the SNMPv1_v2c pseudo-user, those requests execute with administrator rights, letting the low-privilege caller perform actions beyond its intended role. No public proof-of-concept was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Incorrect privilege assignment in Huawei openUBMC causes the SNMP pseudo-identity group (special_users, including the SNMPv1_v2c pseudo-user) to be granted the complete nine-privilege set, so an attacker who already holds valid low-privilege SNMP credentials can drive mapped backend operations as an administrative identity. The flaw sits in route_mapper/account.lua, where get_user_privilege returns full privileges for the SNMP caller identity rather than the caller's actual role; exploitation requires network-reachable SNMP (SNMPv1/v2c community string or SNMP user) and is bounded to operations exposed through the SNMP-to-backend route mapping. It is rated medium severity (CWE-266) with no confirmed active exploitation and no public exploit identified at time of analysis, so it should be treated as a privilege-escalation hardening issue rather than an emergency.
RemediationAI
No vendor-released patch identified at time of analysis, so remediation must initially rely on compensating controls while a firmware fix is confirmed with the vendor via the runZero advisory at https://www.runzero.com/advisories/huawei-openUBMC-snmp-privsec-cve-2026-65199. The most effective immediate control is to disable SNMP on the BMC if it is not operationally required, or restrict the SNMP listener to a dedicated out-of-band management VLAN with ACLs permitting only trusted monitoring hosts - the trade-off is loss of existing SNMP-based monitoring and inventory collection. Where SNMP must remain enabled, migrate away from SNMPv1/v2c to SNMPv3 with authPriv (SHA-2/AES) and per-user credentials, since the vulnerable privilege flattening is tied to the shared pseudo-identity the SNMPv1_v2c path uses; note that SNMPv3 does not by itself remove the incorrect mapping in route_mapper/account.lua, so treat this as risk reduction rather than a fix. Rotate and audit all SNMP community strings and SNMP users, removing credentials from low-privilege or third-party consumers; side effect is disruption of appliances still using the old strings. Restrict BMC network exposure (management interfaces should never be internet-facing), log and alert on SNMP-initiated configuration or account changes, and monitor for backend operations originating from SNMP identities - these controls add operational overhead and alert volume but do not correct the underlying privilege assignment. Apply a vendor firmware release as soon as one is published and re-test that get_user_privilege no longer returns the full nine-privilege set for SNMP pseudo-users.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
openUBMC is the baseboard management controller (BMC) firmware stack, written in Lua, that exposes management functions over interfaces such as SNMP. The root cause is CWE-266 (Incorrect Privilege Assignment): the route mapping layer in route_mapper/account.lua implements a function, get_user_privilege, that resolves an incoming caller identity to a privilege set. Instead of deriving privileges from the specific authenticated SNMP account, it treats SNMP callers as a pseudo-identity that belongs to a hard-coded special_users group, and that group is mapped to all nine defined privileges. Because SNMPv1/v2c offers no real per-user identity model - callers are distinguished only by community string - the pseudo-user SNMPv1_v2c in particular inherits administrative rights. Any SNMP request routed through the mapper therefore executes backend operations with the privileges of an administrator rather than those of the low-privilege SNMP account that originated it, effectively flattening the authorization model for the SNMP transport. The CPE record cpe:2.3:a:huawei:openbmc:*:*:*:*:*:*:*:* indicates the affected firmware is tracked as Huawei openBMC with all versions in scope, and the issue was reported by runZero.
Know when SNMP gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
PR:L because valid low-privilege SNMP credentials are required; AV:N/AC:L as it is network-reachable with no special conditions; admin privilege set enables limited read/modify across mapped operations, so C/I/A:L.
Primary rating from Vendor (runZero).
CVSS VectorVendor: runZero
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Hardcoded/insecure credentials in IDC SFX Series SuperFlex Satellite Receiver. Multiple accounts with known credentials
html5_snmp 1.11 has multiple SQL injection vulnerabilities allowing attackers to manipulate SNMP monitoring database que
SQL injection in LibreNMS 25.12.0 and below. PoC and patch available.
SQL injection in LibreNMS versions 25.12.0 and below allows authenticated users to extract sensitive database informatio
Managed Switch Port Mapping Tool 2.85.2 contains a denial of service vulnerability that allows attackers to crash the ap
html5_snmp 1.11 contains a persistent cross-site scripting vulnerability that allows attackers to inject malicious scrip
Reflected cross-site scripting in LibreNMS versions 25.12.0 and earlier allows unauthenticated remote attackers to injec
Stored XSS in LibreNMS versions 26.1.1 and below allows authenticated administrators to inject malicious scripts through
Stored XSS in LibreNMS versions 26.1.1 and below allows authenticated administrators to inject malicious scripts through
Stored XSS in LibreNMS Alert Rules allows authenticated administrators to inject malicious scripts that execute when oth
Improper SNMP request parsing in Cisco Nexus 9000 Series switches running ACI mode allows authenticated remote attackers
Stored cross-site scripting in LibreNMS versions 24.10.0 through 26.1.1 allows authenticated users to inject malicious s
EUVD-2026-98751
GHSA-246r-j53h-wrm2
NVD
CVE.org
EPSS
Exploit-DB