Missing GSDX SignatureValue verification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Phoenix Contact | PLCnext Engineer | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Phoenixcontact | Plcnext Engineer |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.062% probability within 30 days)
| Link | Providers |
|---|---|
| https://www.certvde.com/en/advisories/VDE-2026-121/ |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Phoenixcontact
Phoenixcontact plcnext Engineer |
|
| Vendors & Products |
Phoenixcontact
Phoenixcontact plcnext Engineer |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | PLCnext Engineer checks GSDX manifest reference digests but does not cryptographically verify the XML `SignatureValue` over canonicalized `SignedInfo`. An unauthenticated local attacker can modify signed GSDML content, update its manifest digest, retain the public certificate data, and leave an invalid nonempty `SignatureValue`. PLCnext Engineer prior to 2026.6 reports the package as `Valid` and selects the modified device description for import under the default policy. | |
| Title | Missing GSDX SignatureValue verification | |
| First Time appeared |
Phoenix Contact
Phoenix Contact plcnext Engineer |
|
| Weaknesses | CWE-347 | |
| CPEs | cpe:2.3:a:phoenix_contact:plcnext_engineer:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Phoenix Contact
Phoenix Contact plcnext Engineer |
|
| References |
| |
| Metrics |
cvssV3_1
|