CVE-2026-29645
Xiangshan Nemu 2025.12
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-29645 is a high-severity Incorrect Calculation of Buffer Size (CWE-131) vulnerability in Xiangshan Nemu. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-29645 is an improper instruction-validation vulnerability in the RISC-V Vector (RVV) decoder of NEMU, an open-source RISC-V emulator maintained under the OpenXiangShan/NEMU project. Specifically, versions of NEMU before v2025.12.r2 fail to correctly validate the funct3 field during decoding of vsetvli, vsetivli, and vsetvl instructions. This allows certain invalid OP-V instruction encodings to be misinterpreted and executed as vset* configuration instructions instead of triggering an illegal-instruction exception.
The vulnerability can be exploited by remote attackers with no privileges or user interaction required, as indicated by its CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). An attacker can provide crafted RISC-V binaries to a system running the affected NEMU version, leading to incorrect trap behavior, architectural state corruption or divergence, and potential denial of service. Exploitation is feasible in environments relying on NEMU for accurate instruction emulation, such as testing, simulation, or sandboxing setups.
Mitigation is available through a patch in NEMU v2025.12.r2 and later versions. The fix is detailed in GitHub commit 481de637d5fc5838356caee80a79e56a33754039, which addresses the issue reported in OpenXiangShan/NEMU issue #952 and merged via pull request #958. Additional technical context on the affected RISC-V Vector instructions is provided in the RISC-V ISA unprivileged vector specification.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-23937
Vulnerability Data
NEMU (OpenXiangShan/NEMU) before v2025.12.r2 contains an improper instruction-validation flaw in its RISC-V Vector (RVV) decoder. The decoder does not correctly validate the funct3 field when decoding vsetvli/vsetivli/vsetvl, allowing certain invalid OP-V instruction encodings to be misinterpreted and executed as vset*…
more
configuration instructions rather than raising an illegal-instruction exception. This can be exploited by providing crafted RISC-V binaries to cause incorrect trap behavior, architectural state corruption/divergence, and potential denial of service in systems that rely on NEMU for correct execution or sandboxing.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.1V1.4.2V2.1.1V2.2.2
Mitigating Controls (NIST 800-53 r5) AI
Developer security testing and code review can discover incorrect buffer-size computations before deployment.
SI-10 directly requires validation of information inputs, which structurally prevents type-validation failures from being introduced or exploitable.
Secure engineering principles directly require correct buffer-size arithmetic and bounds-checked allocation.
Memory-protection mechanisms limit the exploitability of an overflow that results from an incorrect size calculation.
Flaw-remediation processes that include vulnerability scanning or static analysis will surface buffer-size errors.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent buffer-size miscalculations via coding standards, reviews, and testing, while fixing this single weakness only partially fulfills the broader control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards directly require correct buffer-size calculations.
Security testing can detect buffer-size errors before release.
Secure development lifecycle mandates size-checking practices that reduce buffer-size miscalculations.
Application security requirements can specify buffer-size validation rules.
Secure architecture principles include safe memory-allocation guidelines.