CVE-2025-51677

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

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

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

An issue was discovered in openRISC OR1200 commit 83ac6b. An output mismatch between the RTL and the netlist of the or1200 cpu output port can lead to unexpected behavior.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
56(Track)
EG Risk 56/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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 23, 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 Bugs in the LSU · Issue #160 · openrisc/mor1kx · GitHub

https://github.com/openrisc/mor1kx/issues/160#issuecomment-2585618940

Vendor Advisories for CVE-2025-51677(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 37× 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-27 21:01 UTCGHSA enrichment
  2. 2026-07-27 17:16 UTCEG score recompute
  3. 2026-07-27 17:16 UTCGHSA enrichment
  4. 2026-07-27 13:33 UTCGHSA enrichment
  5. 2026-07-27 09:48 UTCGHSA enrichment
  6. 2026-07-27 06:05 UTCGHSA enrichment
  7. 2026-07-27 02:22 UTCGHSA enrichment
  8. 2026-07-26 22:39 UTCGHSA enrichment
  9. 2026-07-26 18:56 UTCGHSA enrichment
  10. 2026-07-26 15:08 UTCEG score recompute
  11. 2026-07-26 15:08 UTCGHSA enrichment
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 11:23 UTCEG score recompute
  14. 2026-07-26 11:23 UTCGHSA enrichment
  15. 2026-07-26 04:36 UTCEG score recompute
  16. 2026-07-26 04:36 UTCGHSA enrichment
  17. 2026-07-25 14:17 UTCEPSS rescore
  18. 2026-07-24 14:17 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 02:58 UTCEG score recompute
  21. 2026-07-23 00:23 UTCEG score recompute
  22. 2026-07-23 00:23 UTCGHSA enrichment
  23. 2026-07-22 14:08 UTCEPSS rescore
  24. 2026-07-22 14:07 UTCEPSS rescore
  25. 2026-07-21 15:24 UTCEPSS rescore
Show 12 more
  1. 2026-07-20 18:38 UTCEG score recompute 9.10
  2. 2026-07-20 18:38 UTCGHSA enrichment
  3. 2026-07-20 18:37 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:30 UTCEG score recompute
  8. 2026-07-19 02:30 UTCGHSA enrichment
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-17 22:01 UTCNVD update
  11. 2026-07-17 19:50 UTCEG score recompute
  12. 2026-07-17 19:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-51677?
CVE-2025-51677 is a critical vulnerability published on July 17, 2026. An issue was discovered in openRISC OR1200 commit 83ac6b. An output mismatch between the RTL and the netlist of the or1200 cpu output port can lead to unexpected behavior.
When was CVE-2025-51677 disclosed?
CVE-2025-51677 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-51677 actively exploited?
CVE-2025-51677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.7% of all scored CVEs.
What is the CVSS score of CVE-2025-51677?
CVE-2025-51677 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-51677?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-51677, 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-51677

Explore →

Is Your Infrastructure Affected by CVE-2025-51677?

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