PatchSiren cyber security CVE debrief
CVE-2025-51679 openRISC CVE debrief
A mismatch between the RTL and netlist in openRISC OR1200 commit 83ac6b can lead to unexpected behavior. This issue has a CVSS score of 9.1 and is considered CRITICAL. The CVE record was published on 2026-08-26T21:16:37.570Z and was last modified on 2026-09-09T16:04:24.933Z. The issue may impact openRISC OR1200 deployments, and defenders should assess exposure and potential impact. The vulnerability class involves a mismatch between RTL and netlist, which can lead to unexpected behavior.
- Vendor
- openRISC
- Product
- OR1200
- CVSS
- CRITICAL 9.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-26
- Original CVE updated
- 2026-09-09
- Advisory published
- 2026-08-26
- Advisory updated
- 2026-09-09
Who should care
Defenders responsible for openRISC OR1200 deployments should assess exposure and potential impact. They should prioritize verification of affected versions and remediation efforts due to the potential for unexpected behavior in openRISC OR1200 deployments. This includes verifying affected versions, assessing exposure, and monitoring for potential exploitation attempts.
Why it matters
Defenders should prioritize verification of affected versions and remediation efforts due to the potential for unexpected behavior in openRISC OR1200 deployments.
- Verification of affected versions is required
- Potential for unexpected behavior in openRISC OR1200 deployments
Technical summary
The issue is caused by a mismatch between the RTL and netlist in openRISC OR1200 commit 83ac6b, which can lead to unexpected behavior. This mismatch may impact the functionality and security of openRISC OR1200 deployments. Defenders should prioritize verification of affected versions and remediation efforts due to the potential for unexpected behavior in openRISC OR1200 deployments. The technical details involve a mismatch between RTL and netlist, which can lead to unexpected behavior in openRISC OR1200 deployments.
Defensive priority
Defenders should prioritize verification of affected versions and remediation efforts.
Recommended defensive actions
- Verify affected versions of openRISC OR1200
- Assess exposure and potential impact
- Monitor for potential exploitation attempts
- Review compensating controls for exposed systems
- Check relevant monitoring, detection, and logs for exposed assets
- Track exceptions, retest remediated assets
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
Evidence notes
The issue is described in the CVE record and NVD vulnerability detail page. Additional information can be found in the source references. The evidence is limited to the provided CVE record and NVD detail page. Defenders should verify the affected versions and assess exposure. The CVE record provides source-provided CVE metadata, and the NVD detail page offers source-specific vulnerability assessment.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-51679 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-51679
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-51679 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-51679
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/openrisc/mor1kx/issues/161
-
Source reference
Unverified legacy reference
URL: https://mason.gmu.edu/~rsaravan/projects/synfuzz/cve/cve.html
-
Source reference
Unverified legacy reference
URL: https://www.arxiv.org/abs/2504.18812
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.