CVE-2019-10926 json
A vulnerability has been identified in SIMATIC MV400 family (All Versions < V7.0.6).
published 2019-06-12 7 y ago modified 2026-06-17 4 mo 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.
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.6affected: 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-08).
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
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-816980.pdf
mitigation, vendor-advisory
-
securityfocus.com
/bid/108725
vdb-entry, third-party-advisory
-
ics-cert.us-cert.gov
/advisories/ICSA-19-162-02
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2019-10926
- NVD CVE-2019-10926
Fencer Vulns 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.