ORIGIN VIEWER · CVE-2026-114558 · Other
NO FIX YET · SEE WHAT TO DO
OriginLab Origin Viewer has an out-of-bounds write when it parses OPJU files, so a crafted file can overwrite memory past an allocated buffer. An attacker who gets a user to open a malicious file or visit a malicious page can run code in the context of the current process.
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.
Anyone who installs Origin Viewer, the free viewer for Origin project files, on Windows and opens OPJU files from outside sources. Exploitation needs the user to open a crafted file or visit a malicious page. Teams that do not use Origin Viewer can skip it.
Not affected if no-origin-viewer-installed, not-installed
Who cares desktop, file-parsing, origin-viewer, windows
10.4.0.25, but those notes do not name this CVE, so do not treat that build as confirmed fixedOriginLab Origin Viewer OPJU File Parsing Out-Of-Bounds Write 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 OPJU files. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated data structure. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-30738.
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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.