Authenticated code execution via absolute upload paths
Published Jul 10, 2026 · Updated Jul 10, 2026
Path injection in OpenPLC Runtime v3 allows remote authenticated users to write arbitrary files through the legacy program-upload workflow. The workflow stores prog_file in Programs.File, then passes it to os.path.join without rejecting absolute paths, so the upload escapes the intended directory. Code execution requires a malicious C++ file to land in the runtime core and an operator to compile and start the program; execution occurs as the runtime user.
Summary
What happened
Path injection in OpenPLC Runtime v3 allows remote authenticated users to write arbitrary files through the legacy program-upload workflow. The workflow stores prog_file in Programs.File, then passes it to os.path.join without rejecting absolute paths, so the upload escapes the intended directory. Code execution requires a malicious C++ file to land in the runtime core and an operator to compile and start the program; execution occurs as the runtime user.
The record
- CVE
- CVE-2026-14480
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- OpenPLC Project
- Product
- OpenPLC Runtime
- Classifications
- CWE-73, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 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=v3
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.
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