{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-65200 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-65200 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-65200 is a low-severity vulnerability in Huawei openBMC, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-65200 and fix it if it is affected.\n\nWhat it is: CVE-2026-65200 is a low-severity vulnerability in Huawei openBMC, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-65200 in the wild and no public exploit code.\n\nAffected product: Huawei openBMC. 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-65200/ (Markdown: https://insights.sbomify.com/CVE-2026-65200/index.md)","id":"CVE-2026-65200","markdown":"https://insights.sbomify.com/CVE-2026-65200/index.md","name":"CVE-2026-65200","record":{"aliases":["GHSA-62hr-2w2v-p8gj"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"openBMC device management","requires_auth":"none","summary":"A malicious on-bus device can trigger an integer underflow in Huawei openBMC, causing out-of-bounds heap reads and potential crashes or data leaks.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"runZero","cpe":[],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-191","name":"Integer Underflow (Wrap or Wraparound)"}],"description":"The openUBMC device-management process parses PLDM-over-MCTP and NCSI-over-MCTP responses from on-bus devices, and three response parsers in the shared transport libraries subtract a fixed header or reserved-field size from a device-supplied response length without a lower-bound check. An undersized response wraps the unsigned length difference to a very large value, and the parser then reads far past the response buffer. The affected code sits in the base (non-vendor) PLDM control class and the Huawei NCSI driver, so it is reachable for any PLDM endpoint or Huawei NIC on the internal management bus, unlike the vendor-specific wangxun parser tracked separately.","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":"Huawei malicious on-bus PLDM or NCSI device can drive out-of-bounds-heap reads via short MCTP responses","id":"CVE-2026-65200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"The reported issue was assessed as intended functionality.","id":"CVE-2026-65202"},"packages":[],"prev":{"headline":"Huawei openUBMC low-privilege SNMP to administrator privilege escalation","id":"CVE-2026-65199"},"products":["openBMC"],"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":["Huawei"]},"summary":"A malicious on-bus device can trigger an integer underflow in Huawei openBMC, causing out-of-bounds heap reads and potential crashes or data leaks.","url":"https://insights.sbomify.com/CVE-2026-65200/"}