OpenBMC IPMI Authentication Bypass via Default userKey and Stale Challenge Value
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-798.
Summary
OpenBMC's IPMI implementation, phosphor-net-ipmid, contains a logic flaw in which an unauthenticated client can force the RAKP Message 1 handler to return before it overwrites the authentication object's constructor defaults. The IPMI service then accepts a RAKP Message 3 whose HMAC is computed with the constant 20-byte 'userKey' initialized from the string '0penBmc' and an often-predictable 'bmcRandomNum'. Several downstream vendors implement phosphor-net-ipmid as their IPMI stack, such as NVIDIA and H3C.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
No affected products listed by the sources yet.
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-16141
- 2026-10-03 Alias added: GHSA-28w7-pg33-g2hj
References
More OpenBMC vulnerabilities
- TI-2024-27723 slpd-lite unauthenticated memory corruption CVSS 3.1CRITICAL 9.8
- TI-2026-13506 OpenBMC IPMI Privilege Escalation via Retargeted RAKP 1 CVSS 3.1HIGH 8.8
Sources
- CVE-2026-16141 · CVE Program
- CVE-2026-16141 · NVD
- FIRST EPSS
- GHSA-28w7-pg33-g2hj · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences