Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessImplant or compromise device on management bus
-
ExploitSend undersized PLDM/NCSI-over-MCTP response
-
ExecutionTrigger unsigned length underflow in parser
-
ImpactOut-of-bounds read leaks BMC memory or crashes process
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer underflow checks
|
| Exploitation Conditions | Exploitation requires an attacker-controlled device on the internal management bus that can return crafted MCTP responses - specifically any PLDM endpoint (reaching the base, non-vendor PLDM control class) or a Huawei NIC speaking NCSI-over-MCTP (reaching the Huawei NCSI driver). The attacker must be able to send an undersized PLDM-over-MCTP or NCSI-over-MCTP response whose length is smaller than the fixed header/reserved-field size the parser subtracts. Explicitly NOT reachable via this CVE is the vendor-specific wangxun parser, which is tracked separately. The decisive limiting factor is physical/on-bus access (AV:P): the attacker must already have a malicious or compromised device on the management bus, so this is not remotely exploitable over the network and not reachable from a normal host OS or external interface. |
| Impact | This is a genuinely low-priority issue, and the available signals agree rather than conflict. The provided CVSS 3.1 vector (AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L, base 3.5) centers on the physical attack vector: exploitation requires a malicious or compromised device already present on the internal management (MCTP) bus, which is the dominant risk-limiting factor. The impact is modest - low confidentiality (out-of-bounds read leaking adjacent BMC memory) and low availability (parser crash), with no integrity impact. No EPSS score was supplied, so exploitation probability cannot be quantified from the input. There is no CISA KEV listing and no public exploit referenced, so the exploitation status is: no public exploit identified at time of analysis. The only intelligence source is a single runZero advisory reporting the flaw; this appears to be a researcher-discovered memory-safety bug rather than an actively targeted vulnerability. Net: despite being a real out-of-bounds read, the physical/on-bus prerequisite and low impact make this a low-urgency patch, not a drop-everything issue. |
| Exploit ScenarioDerived | An attacker who has implanted or compromised a device on the server's internal management bus (a PLDM endpoint or a Huawei NIC presenting NCSI-over-MCTP) returns a deliberately undersized response to the openUBMC device-management process. The parser subtracts a fixed header/reserved-field size without a lower-bound check, underflowing the unsigned length to a huge value and reading far past the response buffer, leaking adjacent BMC memory or crashing the process. No public exploit code is referenced, and the physical-bus requirement (AV:P) makes this a constrained, access-dependent attack. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Out-of-bounds memory reads in the openUBMC device-management process can be induced by a malicious or compromised device on the internal management bus that returns an undersized PLDM-over-MCTP or NCSI-over-MCTP response. Only environments where an attacker already controls a PLDM endpoint (hitting the base, non-vendor PLDM control class) or a Huawei NIC speaking NCSI-over-MCTP are affected; the bug is not reachable over the network or from a normal host OS, since the CVSS 3.1 vector requires physical/bus access (AV:P, base score 3.5) but no authentication (PR:N). An undersized length wraps an unsigned subtraction, causing the parser to read well past the response buffer, yielding limited information disclosure and a low availability impact; no public exploit code has been identified at time of analysis, and the issue is not in CISA KEV.
RemediationAI
No vendor-released patch was identified in the available data, so remediation must currently be compensating. Treat the internal management bus as an untrusted boundary: only attach devices whose firmware provenance and update chain you control, and physically secure or disable unused MCTP/PLDM/NCSI connectors, slots, and mezzanine bays so an adversary cannot insert a malicious endpoint (the CVSS vector AV:P makes physical or on-bus presence the gating prerequisite, so this directly removes the attack path; the trade-off is reduced expandability and added physical-security overhead). Where the platform allows it, segment or disable the management bus path to untrusted PLDM endpoints and restrict Huawei NIC firmware to trusted images, accepting that this may break legitimate out-of-band inventory and health telemetry. Monitor firmware and BMC logs for malformed or abnormally short PLDM/NCSI responses, which may indicate a parsing anomaly, and track the openUBMC project and Huawei security advisories (see the runZero advisory at https://www.runzero.com/advisories/huawei-malicious-device-integer-underflow-cve-2026-65200) for a fixed firmware release adding the missing lower-bound length validation; apply it as soon as it is published. Because the flaw is an out-of-bounds read with low confidentiality and availability impact, prioritize patching below remotely exploitable issues, but remediate if any untrusted device can be placed on the management bus.
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's device-management process communicates with on-bus endpoints using MCTP (Management Component Transport Protocol) as the transport layer, carrying PLDM and NCSI payloads. Three response parsers in the shared transport libraries take a device-supplied response length and subtract a fixed header or reserved-field size before consuming the payload, but perform no lower-bound check. This is a classic CWE-191 integer underflow: when the device reports a length smaller than the fixed constant, the subtraction wraps in unsigned arithmetic to a very large value, and the parser subsequently reads far beyond the end of the response buffer (out-of-bounds read). The affected code lives in the base, non-vendor PLDM control class and the Huawei NCSI driver, which is why any conforming PLDM endpoint or Huawei NIC on the MCTP bus can reach it. The vendor-specific wangxun parser contains a similar weakness but is tracked under a separate CVE and is explicitly out of scope here.
Know when Openbmc 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:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Requires a malicious device on the internal management bus so AV:P; no auth or interaction (PR:N/UI:N); underflow yields an out-of-bounds read (C:L) and possible parser crash (A:L), no integrity impact.
Primary rating from Vendor (runZero).
CVSS VectorVendor: runZero
DescriptionCVE.org
The openUBMC device-management process parses PLDM-over-MCTP and NCSI-over-MCTP responses from on-bus devices, and three response parsers in the shared transport libraries subtract a fixed header or reserved-field size from a device-supplied response length without a lower-bound check. An undersized response wraps the unsigned length difference to a very large value, and the parser then reads far past the response buffer. The affected code sits in the base (non-vendor) PLDM control class and the Huawei NCSI driver, so it is reachable for any PLDM endpoint or Huawei NIC on the internal management bus, unlike the vendor-specific wangxun parser tracked separately.
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
Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
In OpenBMC 2.9, crafted IPMI messages allow an attacker to bypass authentication and gain full control of the system. Ra
Privilege escalation in OpenBMC's phosphor-net-ipmid IPMI stack allows an attacker who already holds a valid low-privile
user_channel/passwd_mgr.cpp in OpenBMC phosphor-host-ipmid before 2020-04-03 does not ensure that /etc/ipmi-pass has str
An authentication bypass in OpenBMC's phosphor-net-ipmid IPMI stack lets a network attacker with no credentials complete
A vulnerability in the combination of the OpenBMC's FW1050.00 through FW1050.10, FW1030.00 through FW1030.50, and FW1020
IBM OpenBMC FW1050.00 through FW1050.10 BMCWeb HTTPS server component could disclose sensitive URI content to an unautho
A vulnerability in bmcweb of OpenBMC Project allows user to cause denial of service. Rated high severity (CVSS 7.5), thi
A vulnerability in bmcweb of OpenBMC Project allows user to cause denial of service. Rated high severity (CVSS 7.5), thi
Arbitrary code execution in IBM OpenBMC FW1060.00 through FW1060.80 is achievable via a path traversal flaw (CWE-22) in
Incorrect privilege assignment in Huawei openUBMC causes the SNMP pseudo-identity group (special_users, including the SN
A limited out-of-bounds memory read in the host-facing BMC firmware management service of IBM OpenBMC can be triggered b
EUVD-2026-98752
GHSA-62hr-2w2v-p8gj
NVD
CVE.org
EPSS
Exploit-DB