CVE-2026-65197
3.1LowPublished 13 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- High
- User interaction
- Required
- Impact
- Limited impact
- Weakness
- CWE-347
Impact
Authenticated admins or users with firmware-update privileges can install malicious, arbitrary firmware on the BMC. This requires network access to the Redfish API and high-privilege credentials.
Root cause
The Redfish UpdateService.UploadSignKey endpoint writes user-uploaded keys directly to /conf/public.pem without proper verification, replacing the trusted signature verification anchor.
Affected systems
H3C HDM Family-A G5 HDM 6.14.01, and H3C HDM Family-A G3/G5 builds containing the Redfish/DRE update tree (HDM2 is not affected).
CVSS v3.1 · CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N
Fix & remediation
Fixed versions are not listed — check the vendor advisory for patch availability. In the interim, restrict network access to the HDM Redfish interface and revoke the firmware-update privilege from non-essential accounts.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
H3C HDM Family-A verifies the RSA signature of a firmware image against a public key it reads from the mutable file `/conf/public.pem`. That file is writable by an authenticated Redfish client through the `UpdateService.UploadSignKey` action, which stores the uploaded body verbatim after validating only that the multipart filename ends in `.pem`. An administrator, or any account with `firmware-update` privilege, can therefore replace the trust anchor with their own key, sign a malicious image with the matching private key, and have it pass verification. Family-A has no hardware root-of-trust (no PFR) to catch the substituted key. This was observed on H3C HDM Family-A G5 HDM 6.14.01. H3C HDM Family-A G3/G5 builds carrying the Redfish/DRE update tree appear to be affected. HDM2 uses a different update path and is not covered by this finding.