Victim-identity code execution via writable project files
Published Jan 16, 2026 · Updated Jan 16, 2026
Missing authorization in AVEVA Process Optimization 2024.1 and earlier allows local users to execute code as an interacting victim. Installation and data-folder ACLs fail to restrict OS Standard Users from altering project files and embedding code for later execution. Exploitation requires local low-privileged access and victim interaction, after which the embedded code runs with the victim's privileges.
Summary
What happened
Missing authorization in AVEVA Process Optimization 2024.1 and earlier allows local users to execute code as an interacting victim. Installation and data-folder ACLs fail to restrict OS Standard Users from altering project files and embedding code for later execution. Exploitation requires local low-privileged access and victim interaction, after which the embedded code runs with the victim's privileges.
The record
- CVE
- CVE-2025-64729
- Published
- Jan 16, 2026
- Updated
- Jan 16, 2026
- Vendor
- AVEVA
- Product
- AVEVA Process Optimization
- Classifications
- CWE-862, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 16, 2026CVE publishedPublication date reported by the CVE source.
- Jan 16, 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=0 <=2024.1
What conditions does exploitation require?
What is affected?
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.
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