CVE-2026-65197: H3C G3/G5 HDM Firmware Verification Key Replacement

Published Oct 13, 2026
·
Updated

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.

Affected Software

1 affected component
H3C HDM Family-A=6.14.01

Event History

Oct 13, 2026
CVE Published
via MITRE·02:17 PM
Data Sourced
via MITRE·02:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which systems are in scope, and which are not?

The finding applies to H3C HDM Family-A G3/G5 builds that carry the Redfish/DRE update tree. It was observed on G5 HDM 6.14.01; HDM2 uses a different update path and is not covered.

2

What level of access does an attacker need?

An attacker needs an authenticated Redfish account with firmware-update privilege, or administrator access. They must upload a replacement .pem signing key, then provide a malicious firmware image signed by the corresponding private key.

3

Are systems protected by a hardware root of trust?

Family-A does not have PFR or another hardware root of trust described for detecting a substituted verification key. Once the mutable public key is replaced, firmware signed with the attacker's matching key can pass verification.

4

How can I determine whether a system may be affected?

Identify whether the device is an H3C HDM Family-A G3 or G5 system with the Redfish/DRE update tree. Review access to the Redfish UpdateService.UploadSignKey action and whether accounts beyond tightly controlled administrators have firmware-update privilege.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203