Skip to main content

OpenRISC OR1200 CVE-2025-51679

| EUVDEUVD-2025-210801 CRITICAL
Sequence of Processor Instructions Leads to Unexpected Behavior (CWE-1281)
2026-08-26 mitre GHSA-f8v4-7pm5-xqfx
9.1
CVSS 3.1 · Vendor: mitre
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain code execution on OR1200 core
  2. Exploit
    Issue crafted instruction sequence
  3. Execution
    Trigger RTL/netlist divergence in hardware
  4. Impact
    Leak internal state or fault core

Vulnerability Assessment

Weakness
CWE
Exploitation Conditions

Exploitation requires that the target hardware was synthesized from the affected OR1200 core at commit 83ac6b such that the RTL-to-netlist mismatch is actually present in the fabricated device or FPGA image, and that the attacker can execute a specific triggering instruction sequence on that core. Limiting factors: the flaw manifests only in the synthesized netlist (RTL-only simulation would not exhibit it), it is tied to a specific commit and synthesis flow, the affected core is a niche open-source soft-core, and there is no evidence the published AV:N (network) vector is real - realistic access is local execution on or design-time control of the core, not remote unauthenticated reach.

Impact

The signals conflict sharply. The published CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:H/A:H, base 9.1) implies trivial remote unauthenticated compromise, but that is implausible for a CPU soft-core: a network attack vector for an RTL/netlist mismatch is unsupported by the description and almost certainly a mis-scored vector - realistic exploitation is local code execution on, or physical/design-time access to, the synthesized core. EPSS is very low (0.15%, percentile 5) and the CVE is not in CISA KEV, so there is no evidence of active exploitation; no POC is provided beyond academic detection tooling. Tags label it 'Information Disclosure,' which is inconsistent with the input vector's C:H/A:H (which claims availability impact but no integrity impact). Bottom line: this is a high-nominal-CVSS but low-real-world-priority research-grade finding for most defenders - verify the actual attack vector with the OpenRISC maintainers before treating the 9.1 as accurate.

Exploit ScenarioDerived

An attacker able to execute code on a device built from the affected OR1200 netlist crafts an instruction sequence that hits the region where synthesized hardware diverges from the verified RTL, causing the core to leak internal state or enter an unexpected fault/hang. Because exploitation depends on the physical/synthesized silicon or FPGA image rather than a network service, the realistic actor is one with local execution or supply-chain/design access; no public exploit code is available, only academic detection tooling.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 27, 2026

Information disclosure in the OpenRISC OR1200 processor soft-core (commit 83ac6b) arises from a mismatch between the RTL source and the synthesized netlist, meaning the fabricated/synthesized hardware behaves differently than the verified design and can leak confidential state or misbehave. The flaw was surfaced by the academic SynFuzz RTL-vs-netlist fuzzing research (arXiv:2504.18812) rather than by field exploitation; no public exploit identified at time of analysis and EPSS is low (0.15%, 5th percentile). The NVD CVSS of 9.1 (C:H/A:H) is far more alarming than the vague one-line description supports, so the score should be treated skeptically.

RemediationAI

No vendor-released patch version is identified at time of analysis - OR1200 is a community RTL project rather than a versioned vendor product, so the primary action is to pull the latest OpenRISC OR1200/mor1kx source past commit 83ac6b and re-run logical-equivalence checking between your RTL and synthesized netlist before taping out or programming FPGAs. Track the upstream issue at https://github.com/openrisc/mor1kx/issues/161 and review the SynFuzz materials (https://www.arxiv.org/abs/2504.18812, https://mason.gmu.edu/~rsaravan/projects/synfuzz/cve/cve.html) to reproduce the detection. As compensating controls for designs already fielded: add formal RTL-vs-netlist equivalence checking to your synthesis flow (trade-off: added EDA tooling cost and runtime), constrain synthesis optimization directives that may have introduced the divergence (trade-off: possible area/timing regression), and restrict who can load bitstreams/run untrusted code on the core (trade-off: operational friction). These are integration-time mitigations; there is no runtime signature to block.

Affected VersionsENISA

n/a n/a

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

OR1200 is a 32-bit RISC CPU implementation of the open OpenRISC 1000 architecture, distributed as synthesizable RTL (Verilog) intended for FPGA/ASIC integration. The root cause is classified as CWE-1281 (sequence of processor instructions / hardware logic leading to unexpected behavior); concretely the defect is an RTL-to-netlist equivalence failure, where logic optimization or synthesis produces a gate-level netlist that is not functionally equivalent to the register-transfer design that was verified. Such mismatches are exactly what the referenced SynFuzz project (mason.gmu.edu synfuzz, arXiv 2504.18812) is built to detect by fuzzing and cross-checking RTL simulation against the post-synthesis netlist. Note the CPE is a placeholder ('cpe:2.3:a:n/a:n/a:*') and one reference actually points to the mor1kx core issue tracker rather than OR1200, so exact affected-component boundaries are not cleanly established in the source data.

Know when N A gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mitre) PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
vuln.today AI 6.3 MEDIUM

A synthesized-hardware mismatch is not network-reachable, so AV:L; triggering the specific divergence with code execution on the core gives AC:H/PR:L, with confidentiality and availability impact but no integrity change.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

Lifecycle Timeline

3
CVSS changed
Aug 27, 2026 - 20:37 NVD
9.1 (CRITICAL)
CVE Published
Aug 26, 2026 - 00:00 cve.org
CRITICAL 9.1
CVE Published
Aug 26, 2026 - 00:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

An issue was discovered in openRISC OR1200 commit 83ac6b. A mismatch between the RTL and netlist can lead to unexpected behavior.

Executive ViewAI

Why It Matters

OpenRISC OR1200 processor soft-core contains an information disclosure vulnerability stemming from a mismatch between verified design and synthesized hardware implementation, potentially allowing confidential data leakage or system misbehavior in affected silicon. Organizations must immediately determine whether this open-source processor core is incorporated into any products or systems, as the CVSS 9.1 rating indicates high-impact confidentiality and availability risks if deployed.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: transitioning to alternative, formally verified processor cores; implementing independent RTL-versus-netlist verification for any OR1200 modifications prior to synthesis; engaging third-party hardware security auditors to validate design-implementation correspondence before silicon fabrication; restricting affected processor versions to non-sensitive applications until remediation is available.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Low
niche open-source CPU soft-core, academic/FPGA/hobbyist use, no broad enterprise footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in N A

View all
CVE-2024-51092 CRITICAL POC
9.1 May 08

LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr

CVE-2025-15684 MEDIUM POC
5.5 Aug 12

Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han

CVE-2024-45257 HIGH POC
7.3 May 08

A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi

CVE-2025-15687 LOW POC
2.1 Aug 12

Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc

CVE-2025-15686 LOW POC
2.1 Aug 12

Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula

CVE-2025-67888 HIGH POC
7.3 May 08

Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root

CVE-2024-53326 HIGH POC
7.3 May 08

LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(

CVE-2026-38360 CRITICAL POC
9.8 May 08

Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti

CVE-2026-30623 CRITICAL POC
9.8 Jul 15

Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr

CVE-2026-67917 CRITICAL POC
9.8 Aug 17

SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg

CVE-2026-75337 CRITICAL POC
9.8 Aug 27

Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ

CVE-2026-31072 CRITICAL POC
9.8 May 19

Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy