Skip to main content
VulnerabilityPublished Updated

CVE-2026-29642: Internal Asset Exposed to Unsafe Debug Access Level or State

Source CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

Until a patch is available, limit local privileged access to trusted users only and monitor for unusual behavior related to CSR operations. Avoid executing untrusted firmware or software that could induce privileged CSR operations.

Description

CVE-2026-29642 is a high-severity vulnerability affecting certain versions of the XiangShan RISC-V implementation. A local attacker with privileges to execute CSR operations or induce firmware to do so can perform crafted reads/writes to the menvcfg register. This can cause reserved WPRI bits in the xstatus register to be incorrectly set to 1, violating the RISC-V specification that these bits must not be modified by software. The vulnerability has a CVSS score of 7.8, indicating high impact on confidentiality, integrity, and availability. No patch or official remediation guidance is currently available, and no known exploits have been reported in the wild. The vulnerability specifically involves improper handling of WPRI fields during menvcfg accesses in affected XiangShan versions as of November 19, 2024.

References

Community reviews

Loading reviews…