Loading vulnerability…
CVE-2026-14480 is an authenticated arbitrary file write vulnerability in OpenPLC Runtime v3 affecting the legacy web UI program-upload workflow. The flaw arises because the application stores an attacker-controlled filename supplied through the prog_file parameter in the Programs.File database field and later reuses that value as the destination path for an uploaded file without validating or constraining it to an intended upload directory. Because the implementation relies on Python path handling in a way that permits attacker-controlled absolute paths, a low-privileged authenticated user can cause uploaded content to be written to arbitrary filesystem locations writable by the OpenPLC webserver process. In the default OpenPLC build pipeline, C++ source files placed in the runtime core directory are automatically compiled into the runtime binary. As a result, the arbitrary file write can be escalated to arbitrary native code execution by placing a malicious .cpp file in that directory and waiting for a normal program compilation and runtime start.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.