# CVE-2026-29642: Other in n/a

> A local attacker can manipulate reserved status bits via privileged CSR operations, potentially bypassing security controls in XiangShan processors.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-9m35-v5wh-m3xw

## What is CVE-2026-29642?

CVE-2026-29642 is a high-severity vulnerability in n/a, published on 20 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A local attacker who can execute privileged CSR operations (or can induce firmware to do so) performs carefully crafted reads/writes to menvcfg (e.g., csrrs in M-mode). On affected XiangShan versions (commit aecf601e803bfd2371667a3fb60bfcd83c333027, 2024-11-19), these menvcfg accesses can unexpectedly set WPRI (reserved) bits in the status view (xstatus) to 1. RISC-V defines WPRI fields as "writes preserve values, reads ignore values," i.e., they must not be modified by software manipulating other fields, and menvcfg itself contains multiple WPRI fields.

Weakness: CWE-1244 (Internal Asset Exposed to Unsafe Debug Access Level or State)

## Which versions are affected by CVE-2026-29642?


## How do I fix CVE-2026-29642?

No fix has been published for CVE-2026-29642 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-29642 being exploited?

There is no known exploitation of CVE-2026-29642 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29642 and fix it if it is affected.

What it is: CVE-2026-29642 is a high-severity vulnerability in n/a, published on 20 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29642 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29642/ (Markdown: https://insights.sbomify.com/CVE-2026-29642/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29642
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29642
- OSV: https://osv.dev/vulnerability/CVE-2026-29642

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29642/
Summaries are generated and may contain mistakes; the official description above is the record.