Read the docs
TI-2026-71786 Aliases CVE-2026-65198GHSA-5754-6w67-33hx

Hard-coded SNMPv3 USM key in Huawei openUBMC

Priority MEDIUM 42CWE-321Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · High · Low
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-321.

Summary

Huawei openUBMC through 26.06 ships a hard-coded SNMPv3 USM key (CWE-321) that uses the same value for both authentication and privacy. An attacker who holds the key, which is recoverable from the open source build, can authenticate to and decrypt SNMPv3 traffic from units that still carry the shipped key. SNMP access maps to full device administration, including system reset and firmware upgrades.

Written with Claude Haiku 5.5 from the sources below · 2026-10-27

Description from the CNA

Huawei's openUBMC ships a default SNMPv3 USM key that uses one value for both authentication and privacy. An attacker who holds the key (recoverable from the open-source build) can authenticate SNMPv3 to, and decrypt SNMPv3 traffic from, any unit that still carries the shipped key. The build customization `manifest/build/customization/default_password.lua` sets `AuthenticationKey == EncryptionKey == 7df2f29369e3ac3245b2c9d46b67a0ecd055197e41808a34ef325db2f6422581` for the iBMC product build, and the community seed `account/manufacture/default_password.lua` sets both to `7a2f5b86f20233ec7b7bef49643fbf34d86d0cbf6f1f8f5c52d4f30d4536938b`. These are shipped constants, not per-unit values, and they are not rotated by the Administrator password reset, so they survive account provisioning. This is especially dangerous considering that SNMP access is mapped to full device administration privileges, including system reset and firmware upgrades.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00189 8th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
HuaweiopenUBMCup to 26.06—No fix listedCNA
  • openUBMC VendorHuawei Affected up to 26.06 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for openUBMC.

Written with Claude Haiku 5.5 from the sources below · 2026-10-27

Timeline

  1. 2026-10-13 Threatist record created from CVE-2026-65198
  2. 2026-10-13 Alias added: GHSA-5754-6w67-33hx
  3. 2026-10-14 Priority changed: MEDIUM → LOW
  4. 2026-10-15 CISA SSVC decision points changed
  5. 2026-10-15 Priority changed: LOW → MEDIUM

References

  • TI-2019-00485 Use after free in Microsoft Windows KEVCVSS 3.1CRITICAL 9.8
  • TI-2016-02580 Code injection in Apache Struts through Dynamic Method Invocation KEVCVSS 3.1HIGH 8.1
  • TI-2020-00067 Out-of-bounds write in Android KEVCVSS 3.1HIGH 7.8
  • TI-2019-01829 Use after free in Android KEVCVSS 3.1HIGH 7.8
  • TI-2017-10594 Heap-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a… CVSS 3.1CRITICAL 9.8
  • TI-2017-12631 Improper input validation in Huawei HG532 CVSS 3.0HIGH 8.8
See all 2424 →

Sources