{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-65197 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-65197 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-65197 is a low-severity vulnerability in H3C HDM Family-A G5, published on 13 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-65197 and fix it if it is affected.\n\nWhat it is: CVE-2026-65197 is a low-severity vulnerability in H3C HDM Family-A G5, published on 13 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-65197 in the wild and no public exploit code.\n\nAffected product: H3C HDM Family-A G5. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-65197/ (Markdown: https://insights.sbomify.com/CVE-2026-65197/index.md)","id":"CVE-2026-65197","markdown":"https://insights.sbomify.com/CVE-2026-65197/index.md","name":"CVE-2026-65197","record":{"aliases":["GHSA-3886-vrm6-hhxp"],"analysis":{"component_type":"hardware_firmware","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"H3C HDM firmware","requires_auth":"high_privilege","summary":"Authenticated attackers can replace the firmware verification key to install malicious firmware, bypassing signature checks on H3C HDM devices.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"runZero","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"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. \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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"H3C G3/G5 HDM Firmware Verification Key Replacement","id":"CVE-2026-65197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Huawei Default SNMPv3 USM key","id":"CVE-2026-65198"},"packages":[],"prev":{"headline":"Avocent ACS8000 wsserver command injection","id":"CVE-2026-65184"},"products":["HDM Family-A G5"],"published":"2026-10-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["H3C"]},"summary":"Authenticated attackers can replace the firmware verification key to install malicious firmware, bypassing signature checks on H3C HDM devices.","url":"https://insights.sbomify.com/CVE-2026-65197/"}