Skip to content
Fencer Intel
medium 5.3

CVE-2019-10926 json

A vulnerability has been identified in SIMATIC MV400 family (All Versions < V7.0.6).

published 7y ago modified 4mo ago also EUVD-2019-2640

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

A vulnerability has been identified in SIMATIC MV400 family (All Versions < V7.0.6). Communication with the device is not encrypted. Data transmitted between the device and the user can be obtained by an attacker in a privileged network position. The security vulnerability can be exploited by an attacker in a privileged network position which allows eavesdropping the communication between the affected device and the user. The user must invoke a session. Successful exploitation of the vulnerability compromises confidentiality of the data transmitted.

Is CVE-2019-10926 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-19-162-02 updated cvss 5.3

Siemens SIMATIC Ident MV440 Family (Update A)

  • Siemens SIMATIC MV400 family <V7.0.6
    affected: fixed in V7.0.6, mitigation

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Exploit prediction

1.55% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 2.6 AV:N/AC:H/Au:N/C:P/I:N/A:N

Affected products

  • Siemens SIMATIC MV400 family

Classification

Weakness
  • CWE-319 Cleartext Transmission of Sensitive Information
  • CWE-310 Cryptographic Issues

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.