User-context code execution via unchecked OPJU parser write
Published Aug 20, 2026 · Updated Aug 20, 2026
Out-of-bounds write in OriginLab OriginPro 2026b SR0 and earlier allows context-dependent attackers to execute code via a crafted OPJU file. The OPJU parser insufficiently validates file-supplied data before writing it beyond an allocated data structure, causing heap corruption. A target user must open the file; successful exploitation runs arbitrary code with that user's privileges.
Summary
What happened
Out-of-bounds write in OriginLab OriginPro 2026b SR0 and earlier allows context-dependent attackers to execute code via a crafted OPJU file. The OPJU parser insufficiently validates file-supplied data before writing it beyond an allocated data structure, causing heap corruption. A target user must open the file; successful exploitation runs arbitrary code with that user's privileges.
The record
- CVE
- CVE-2026-18288
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- OriginLab Corporation
- Product
- OriginPro
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2026 SR1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo