ORIGIN VIEWER · CVE-2026-114563 · Other
NO FIX YET · SEE WHAT TO DO
Origin Viewer, OriginLab's viewer for Origin data files, has a stack-based buffer overflow in OGWU file parsing (length of user data not validated before copying to a stack buffer). ZDI rates it CVSS 7.8 (local, user interaction required): a user must open a malicious file or visit a malicious page. Code runs in the context of the Origin Viewer process. ZDI credits rgod and says OriginLab has issued an update; no exploitation or public PoC found. Anyone with Origin Viewer installed who opens OGWU files from outside sources is exposed; the affected version range is not published. Machines without Origin Viewer can skip it.
first public Nov 12, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that install OriginLab Origin Viewer and open OGWU files, whether from email, downloads or web pages. The sources do not list affected version ranges. Systems without Origin Viewer are not exposed.
Not affected if not-installed, origin-viewer-not-installed
Who cares desktop, file-parsing, origin-viewer, user-interaction, windows
OriginLab Origin Viewer OGWU File Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of OriginLab Origin Viewer. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the parsing of OGWU files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-30737.
This page as .md · .json · CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.