CVE
CODESYS Automation Server Connector path traversal in connector allows arbitrary file writes
Only affects CODESYS Automation Server Connector versions from 1.23.0.0 before 1.40.0.0 when scripting commands run through the affected interface. Fixed in 1.40.0.0.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 1.40.0.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. CODESYS Automation Server Connector versions from 1.23.0.0 up to but not including 1.40.0.0 are affected. Successful exploitation requires execution of commands via the affected scripting interface.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.62% · 50th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The CODESYS Automation Server Connector is affected by a path traversal flaw: it trusts file names supplied by a server without checking them properly. An attacker without logging in can reach it remotely, but a user must first be tricked into trusting a malicious Automation Server or the connection must be intercepted; the attacker can then write files to arbitrary locations on the engineering workstation and potentially run code with that user's privileges.
Original description
The CODESYS Automation Server Connector uses server-supplied file names without sufficient path traversal checks. An unauthenticated remote attacker controlling a malicious Automation Server and tricking a user to trust it, or performing a man-in-the-middle attack on a trusted communication channel, can exploit this vulnerability to write attacker-controlled files to arbitrary locations on the engineering workstation and subsequently achieve arbitrary code execution with user privileges.
Who should check
Engineering teams running the CODESYS Automation Server Connector add-on from 1.23.0.0 up to 1.40.0.0 with the CODESYS Development System
“vers:generic/>=1.23.0.0|<1.40.0.0”
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 7.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
CODESYS Automation Server Connector versions from 1.23.0.0 up to but not including 1.40.0.0 are affected. Successful exploitation requires execution of commands via the affected scripting interface.Upgrade to a fixed version: 1.40.0.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-118498 (Improper Limitation of a Pathname to a Restricted Directory in CODESYS Automation Server Connector), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-118498 (entry last updated 2026-11-17):
Affected:
- CODESYS Automation Server Connector: from 1.23.0.0, fixed in 1.40.0.0
Fixed versions: 1.40.0.0.
Conditions (all must be true for the bug to be hit):
- CODESYS Automation Server Connector versions from 1.23.0.0 up to but not including 1.40.0.0 are affected. (source: https://certvde.com/en/advisories/VDE-2026-146/)
- Successful exploitation requires execution of commands via the affected scripting interface. (source: https://certvde.com/en/advisories/VDE-2026-146/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-118498 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118498 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.certvde.com/en/advisories/VDE-2026-146/
- https://certvde.com/en/advisories/VDE-2026-146/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-118498
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-118498"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- CODESYS Automation Server Connector
From 1.23.0.0 · fixed in 1.40.0.0
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-118498
Is CVE-2026-118498 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A flaw in how the product limits file paths lets an attacker write attacker-controlled files to arbitrary locations on the engineering workstation. This may lead to remote code execution with the privileges of the user running the CODESYS Development System.Source: certvde.com
Which versions are affected by CVE-2026-118498?
Automation Server Connector: from 1.23.0.0 before 1.40.0.0.Source: cve.now feed data
Am I affected, and how do I check?
CODESYS Automation Server Connector versions from 1.23.0.0 up to but not including 1.40.0.0 are affected. The exposure requires commands to be executed through the affected scripting interface, so check the installed Automation Server Connector version and whether that scripting interface is in use.Source: certvde.com
How do I fix CVE-2026-118498?
Update CODESYS Automation Server Connector to version 1.40.0.0.Source: certvde.com