CVE-2026-14480: OpenPLC v3 External Control of File Name or Path
OpenPLC Runtime v3 contains an authenticated arbitrary file write vulnerability in the legacy web UI program‑upload workflow. The application stores an attacker‑supplied filename (progfile) directly into the Programs.File database field and later uses this value as the destination path for an uploaded file without validating or restricting the path. Because Python os.path.join() honors attacker‑controlled absolute paths, an authenticated user can write arbitrary files anywhere writable by the OpenPLC webserver process. In the default build pipeline, all C++ source files within the OpenPLC runtime core directory are automatically compiled into the executable runtime binary. By writing a malicious .cpp file into this directory, an authenticated attacker can escalate the arbitrary file write into arbitrary native code execution when the operator triggers a normal program compilation and runtime start.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenPLC Runtimeto a version that resolves this vulnerability.Fixed in OpenPLC v4 - Operational
After upgrading, treat any uploaded program file(s) from the legacy web UI program-upload workflow as potentially malicious and recompile/build from known-good sources as operators trigger normal program compilation.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-14480?
CVE-2026-14480 has a critical severity score of 9.9.
How do I fix CVE-2026-14480?
To fix CVE-2026-14480, apply the latest security patches provided by OpenPLC.
What type of vulnerability is CVE-2026-14480?
CVE-2026-14480 is an authenticated arbitrary file write vulnerability.
What software is affected by CVE-2026-14480?
CVE-2026-14480 affects OpenPLC Runtime v3.
What impact does CVE-2026-14480 have?
CVE-2026-14480 allows an attacker to write arbitrary files to the system, potentially leading to a complete compromise.