CVE-2026-110935Phoenix Contact PLCnext Engineer path traversal
CVE-2026-110935 is a path traversal in Phoenix Contact PLCnext Engineer, rated high (8.6 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
A file name from the request can climb out of the intended folder with sequences like ../, reaching files the service never meant to expose.
How it is reached
An attacker can exploit it by someone who can already run code or sign in on the machine, without an account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker read or write files outside the folders the service meant to expose.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.19% chance of exploitation activity in the next 30 days, higher than 9% of scored CVEs.
What to do
- Upgrade Phoenix Contact PLCnext Engineer to 2026.6 or later.
- Limit who can run code or sign in on the hosts that run it.
Description from NVD
The PFI plugin framework deployment routine does not validate path components when extracting archive entries to the local plugin repository. Archive entries containing relative path segments such as '..' are not rejected, allowing an unauthenticated local attacker to write files outside the plugin repository to arbitrary locations accessible with the current user's permissions which could result in full system compromise.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- File storage the service can read or write. The flaw sits between the application and the file system it can reach.
Trust boundaries in play
- Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
- Between the application and the file system it can reach. An attacker who crosses it can read or write files outside the folders the service meant to expose.
Questions to answer about your own systems
- Where does Phoenix Contact PLCnext Engineer run in your systems, and at which version?
- Which of those hosts also run code or users you do not fully trust?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.