# CVE-2026-29648: Privilege escalation in n/a

> Less-privileged code can bypass isolation controls to read or write sensitive CSRs in OpenXiangShan NEMU when Smstateen is enabled.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-2vgw-r373-m9qx

## What is CVE-2026-29648?

CVE-2026-29648 is a high-severity vulnerability in n/a, published on 20 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In OpenXiangShan NEMU, when Smstateen is enabled, clearing mstateen0.ENVCFG does not correctly restrict access to henvcfg and senvcfg. As a result, less-privileged code may read or write these CSRs without the required exception, potentially bypassing intended state-enable based isolation controls in virtualized or multi-privilege environments.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-29648 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29648 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29648 is a high-severity vulnerability in n/a, published on 20 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29648 exists.

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-29648/ (Markdown: https://insights.sbomify.com/CVE-2026-29648/index.md)
```

## Sources

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

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