CVE-20XX-?

CVE-2026-65197

3.1 LOW 0.1% exploit odds No fix listed Crypto Device

What it is

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.

At a glance

Exploitability
Can be exploited over the network with an admin-level account, but needs a user to act. Limited direct impact.
Exploit odds
0.1% chance of exploitation in the next 30 days (EPSS).
Fix
No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

  1. PublishedDisclosed publicly on CVE.org and NVD
  2. Last updatedMost recent change to the record

Details

Published
Last modified
Exploit probability
0.1% · EPSS, next 30 days
Weakness
CWE-347
Record status
Deferred

Attack profile CVSS 3.1 · 3.1

Attack vector
Network
Complexity
High
Privileges needed
High
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
Raw vector

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N

Meme: I wake up, CVE-2026-65197
Download Square Reddit

References

NVD record · CVE.org record