# CVE-2026-14480: OpenPLC v3 External Control of File Name or Path

> Authenticated attackers can write arbitrary files via path traversal, leading to native code execution during compilation in OpenPLC Runtime.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-gx73-gv82-355v

## What is CVE-2026-14480?

CVE-2026-14480 is a high-severity path traversal vulnerability in OpenPLC, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2026-14480?


## How do I fix CVE-2026-14480?

No fix has been published for CVE-2026-14480 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14480 being exploited?

There is no known exploitation of CVE-2026-14480 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14480 and fix it if it is affected.

What it is: CVE-2026-14480 is a high-severity path traversal vulnerability in OpenPLC, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14480 in the wild and no public exploit code.

Affected product: OpenPLC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14480/ (Markdown: https://insights.sbomify.com/CVE-2026-14480/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14480
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14480
- OSV: https://osv.dev/vulnerability/CVE-2026-14480

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14480/
Summaries are generated and may contain mistakes; the official description above is the record.