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

> Local attackers can tamper with Physical Memory Attribute settings in XiangShan processors, potentially leading to privilege escalation or information disclosure.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 21 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-p2hj-qw82-grpc

## What is CVE-2026-29644?

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

### Official description

XiangShan (open-source high-performance RISC-V processor) commit edb1dfaf7d290ae99724594507dc46c2c2125384 (2024-11-28) has improper gating of its distributed CSR write-enable path, allowing illegal CSR write attempts to alter custom PMA (Physical Memory Attribute) CSR state. Though the RISC-V privileged specification requires an illegal-instruction exception for non-existent/illegal CSR accesses, affected XiangShan versions may still propagate such writes to replicated PMA configuration state. Local attackers able to execute code on the core (privilege context depends on system integration) can exploit this to tamper with memory-attribute enforcement, potentially leading to privilege escalation, information disclosure, or denial of service depending on how PMA enforces platform security and isolation boundaries.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-29644 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29644 is a medium-severity vulnerability in n/a, published on 21 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-29644 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-29644/ (Markdown: https://insights.sbomify.com/CVE-2026-29644/index.md)
```

## Sources

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

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