CVE-2026-65197: Software Security Vulnerability Vulnerability

LOW
Advisory Identifier: GHSA-3886-vrm6-hhxp
Share
CVSS 3.1
CWE-347
Published
Advisory Summary

CVE-2026-65197 is a LOW (CVSS 3.1) security vulnerability vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not verify, or incorrectly verifies, the cryptographic signature for data.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-65197 at a Glance

CVE Identifier CVE-2026-65197
GHSA Identifier GHSA-3886-vrm6-hhxp
Severity LOW
CVSS v3.1 Base Score 3.1
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 3.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required High (PR:H)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-65197

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-65197, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-65197 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-65197
www.runzero.com/advisories/h3c-hdm-... WEB
https://www.runzero.com/advisories/h3c-hdm-firmware-verification-key-replacement-cve-2026-65197

Frequently Asked Questions

What is CVE-2026-65197?
CVE-2026-65197 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-347: Improper Verification of Cryptographic Signature.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-65197?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-65197?
CVE-2026-65197 has a CVSS v3.1 base score of 3.1 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2026-65197?
CVE-2026-65197 is classified under CWE-347: Improper Verification of Cryptographic Signature (The product does not verify, or incorrectly verifies, the cryptographic signature for data.).
How can I check Maven dependencies for CVE-2026-65197?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3886-vrm6-hhxp",
  "modified" : "2026-10-13T15:32:27Z",
  "published" : "2026-10-13T15:32:27Z",
  "aliases" : [ "CVE-2026-65197" ],
  "details" : "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. \n\nThis 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-65197"
  }, {
    "type" : "WEB",
    "url" : "https://www.runzero.com/advisories/h3c-hdm-firmware-verification-key-replacement-cve-2026-65197"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "LOW",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-13T15:17:46Z"
  }
}