CVE
CODESYS Automation Server Connector man-in-the-middle via improper certificate validation
Affects CODESYS Automation Server Connector and CODESYS Service Tool from 1.0.0.0 before 1.40.0.0 when a user starts certificate enrollment with a CODESYS Automation Server. 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:N/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. The bug is hit when a user starts the certificate enrollment with a CODESYS Automation Server. Affected versions are CODESYS Automation Server Connector and CODESYS Service Tool from 1.0.0.0 before 1.40.0.0.
- 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.21% · 11th 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? →
- 20/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
Improper certificate validation in CODESYS Automation Server Connector and CODESYS Service Tool lets a remote attacker without logging in carry out a man-in-the-middle attack. When a user starts certificate enrollment, the attacker can supply an untrusted certificate that gets accepted as trusted, allowing them to intercept and manipulate communications between the CODESYS Automation Server and the PLC network.
Original description
The affected products do not sufficiently validate CODESYS Automation Server TLS certificates when a user starts the certificate enrollment. An unauthenticated remote attacker performing a man-in-the-middle attack can exploit this vulnerability by supplying an untrusted certificate that is accepted as trusted. Successful exploitation may allow an attacker to intercept and manipulate communications between the CODESYS Automation Server and the PLC network.
Who should check
Teams running CODESYS Automation Server Connector or CODESYS Service Tool before 1.40.0.0, including those configuring CODESYS Edge Gateways.
“vers:generic/>=1.0.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.4/10CVSS 7.4, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
The bug is hit when a user starts the certificate enrollment with a CODESYS Automation Server. Affected versions are CODESYS Automation Server Connector and CODESYS Service Tool from 1.0.0.0 before 1.40.0.0.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-118497 (Improper Certificate Validation in CODESYS Automation Server Connector and CODESYS Service Tool), 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-118497 (entry last updated 2026-11-17):
Affected:
- CODESYS Automation Server Connector: from 1.0.0.0, fixed in 1.40.0.0
- CODESYS Service Tool: from 1.0.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):
- The bug is hit when a user starts the certificate enrollment with a CODESYS Automation Server. (source: https://certvde.com/en/advisories/VDE-2026-145/)
- Affected versions are CODESYS Automation Server Connector and CODESYS Service Tool from 1.0.0.0 before 1.40.0.0. (source: https://certvde.com/en/advisories/VDE-2026-145/)
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-118497 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118497 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-145/
- https://certvde.com/en/advisories/VDE-2026-145/
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-118497
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-118497"}.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.0.0.0 · fixed in 1.40.0.0
- CODESYS Service Tool
From 1.0.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-118497
Is CVE-2026-118497 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?
The products do not properly validate certificates, so an attacker could intercept and manipulate communications between the CODESYS Automation Server and the PLC network.Source: certvde.com
Which versions are affected by CVE-2026-118497?
Automation Server Connector: from 1.0.0.0 before 1.40.0.0. Service Tool: from 1.0.0.0 before 1.40.0.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 1.0.0.0 before 1.40.0.0 of CODESYS Automation Server Connector and CODESYS Service Tool are in scope. The bug is hit when a user starts certificate enrollment with a CODESYS Automation Server, so compare the installed version of each product against that range.Source: certvde.com
How do I fix CVE-2026-118497?
Update both CODESYS Automation Server Connector and CODESYS Service Tool to version 1.40.0.0.Source: certvde.com