# CVE-2025-51678: Other in n/a

> A mismatch in PCPI instruction and memory address in PicoRV32 can cause unexpected behavior, requiring a patch for hardware designers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-79r2-fcgx-3m82

## What is CVE-2025-51678?

CVE-2025-51678 is a high-severity vulnerability in n/a, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in RISC-V PicoRV32 commit 87c89a. A mismatch in the PCPI INSN and memory address can lead to unexpected behavior.

Weakness: CWE-704 (Incorrect Type Conversion or Cast), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-51678?


## How do I fix CVE-2025-51678?

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

## Is CVE-2025-51678 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-51678 and fix it if it is affected.

What it is: CVE-2025-51678 is a high-severity vulnerability in n/a, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-51678 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-2025-51678/ (Markdown: https://insights.sbomify.com/CVE-2025-51678/index.md)
```

## Sources

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

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