Vulnerability in OpenPLC Runtime (CVE-2026-14480)
Summary
Vulnerability in OpenPLC Runtime (CVE-2026-14480). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
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 (prog_file) 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.
Source: CISA ICS Advisories NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-14480 has been found in OpenPLC Runtime.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "OpenPLC Runtime CVE-2026-14480" on the vendor's site.
CVE-2026-14480 (OpenPLC Runtime) — CWE-73 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-73) exists in OpenPLC Runtime.
Check the vendor advisory for the affected versions of OpenPLC Runtime.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで OpenPLC Runtime を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web ics-cert@hq.dhs.gov
- web nvd.nist.gov
- web ics-cert@hq.dhs.gov
- web github.com