CVE-2026-65197
H3C G3/G5 HDM Firmware Verification Key Replacement
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.
INFO
Published Date :
Oct. 13, 2026, 3:17 p.m.
Last Modified :
Oct. 13, 2026, 3:17 p.m.
Remotely Exploit :
Yes !
Source :
44488dab-36db-4358-99f9-bc116477f914
Affected Products
The following products are affected by CVE-2026-65197
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 44488dab-36db-4358-99f9-bc116477f914 | |||||
| CVSS 3.1 | LOW | 44488dab-36db-4358-99f9-bc116477f914 | ||||
| CVSS 3.1 | LOW | MITRE-CVE |
Solution
- Restrict firmware update privileges.
- Implement secure management of public key files.
- Ensure firmware image integrity checks are robust.
- Apply vendor-provided security updates promptly.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-65197.
| URL | Resource |
|---|---|
| https://www.runzero.com/advisories/h3c-hdm-firmware-verification-key-replacement-cve-2026-65197 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-65197 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-65197
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-65197 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-65197 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 44488dab-36db-4358-99f9-bc116477f914
Oct. 13, 2026
Action Type Old Value New Value Added 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. Added CVSS V3.1 AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N Added CWE CWE-347 Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/65xxx/CVE-2026-65197.json">CVE-2026-65197</a> Added Reference https://www.runzero.com/advisories/h3c-hdm-firmware-verification-key-replacement-cve-2026-65197 Added SSVC {'role': 'CNA', 'options': [{'exploitation': 'poc'}, {'automatable': 'no'}, {'technicalImpact': 'total'}], 'version': '2.0.3'}