An issue was discovered in RISC-V PicoRV32 commit 87c89a. A mismatch in the PCPI INSN and memory address can lead to unexpected behavior.
CVE-2025-51678
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 35.3%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
July 20, 2026
Advisory Details (3)
Auto-updated Jul 20, 2026[2504.18812] SynFuzz: Leveraging Fuzzing of Netlist to Detect Synthesis Bugs
https://www.arxiv.org/abs/2504.18812Synthesis Bug : Mismatch in PCPI INSN and Memory Address · Issue #269 · YosysHQ/picorv32 · GitHub
https://github.com/YosysHQ/picorv32/issues/269Vendor Advisories for CVE-2025-51678(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 18× in last 7d / 18× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 02:58 UTCEG score recompute
- 2026-07-23 00:23 UTCEG score recompute
- 2026-07-23 00:23 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:07 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 18:38 UTCEG score recompute▲ 7.50
- 2026-07-20 18:38 UTCGHSA enrichment
- 2026-07-20 18:37 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:31 UTCEG score recompute
- 2026-07-19 02:30 UTCGHSA enrichment
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-17 22:01 UTCNVD update
- 2026-07-17 20:15 UTCEG score recompute
- 2026-07-17 20:14 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2025-51678?
When was CVE-2025-51678 disclosed?
Is CVE-2025-51678 actively exploited?
What is the CVSS score of CVE-2025-51678?
How do I remediate CVE-2025-51678?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-51678
Is Your Infrastructure Affected by CVE-2025-51678?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.