CVE-2026-110021: PLCnext Engineer checks GSDX manifest reference digests but does not cryptographically verify the
Source GCVE Database
Not known to be exploited · CVSS 6.9 Medium : upgrade to 2026.6 when convenient.
Data as of 4 Nov 2026, 15:29 UTC
Thin evidence
One scorer or none| CNA (CERTVDE) | CVSS 4.0 | 6.9 |
|---|---|---|
| CNA (CERTVDE) | CVSS 3.1 | 6.2 |
- Patch
- Available – fixed in 2026.6
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Upgrade PLCnext Engineer to 2026.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Phoenix ContactPLCnext Engineer | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict local access to trusted users only to prevent unauthorized modification of GSDML files.
Description
PLCnext Engineer versions prior to 2026.6 do not cryptographically verify the XML SignatureValue over the canonicalized SignedInfo in GSDX manifest files. This allows an unauthenticated local attacker to modify signed GSDML content, update its manifest digest, and retain the public certificate data while leaving an invalid nonempty SignatureValue. Despite the invalid signature, the software reports the package as valid and imports the modified device description under the default policy.