CVE-2025-51678

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

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 computed
Severity75% × 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
No patch confirmed yet.
generic

[2504.18812] SynFuzz: Leveraging Fuzzing of Netlist to Detect Synthesis Bugs

https://www.arxiv.org/abs/2504.18812
generic

Synthesis Bug : Mismatch in PCPI INSN and Memory Address · Issue #269 · YosysHQ/picorv32 · GitHub

https://github.com/YosysHQ/picorv32/issues/269

Vendor 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.

  1. 2026-07-23 02:58 UTCEG score recompute
  2. 2026-07-23 00:23 UTCEG score recompute
  3. 2026-07-23 00:23 UTCGHSA enrichment
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:07 UTCEPSS rescore
  6. 2026-07-21 15:24 UTCEPSS rescore
  7. 2026-07-20 18:38 UTCEG score recompute 7.50
  8. 2026-07-20 18:38 UTCGHSA enrichment
  9. 2026-07-20 18:37 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:30 UTCEPSS rescore
  12. 2026-07-19 14:30 UTCEPSS rescore
  13. 2026-07-19 02:31 UTCEG score recompute
  14. 2026-07-19 02:30 UTCGHSA enrichment
  15. 2026-07-19 02:28 UTCEPSS rescore
  16. 2026-07-17 22:01 UTCNVD update
  17. 2026-07-17 20:15 UTCEG score recompute
  18. 2026-07-17 20:14 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-51678?
CVE-2025-51678 is a high vulnerability published on July 17, 2026. An issue was discovered in RISC-V PicoRV32 commit 87c89a. A mismatch in the PCPI INSN and memory address can lead to unexpected behavior.
When was CVE-2025-51678 disclosed?
CVE-2025-51678 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-51678 actively exploited?
CVE-2025-51678 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-51678?
CVE-2025-51678 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-51678?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-51678, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-51678

Explore →

Is Your Infrastructure Affected by CVE-2025-51678?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.