All changessiemensas of 2026-09-07
CVE-2023-28831
siemenssimatic et 200sp cpu 1510sp f-1 pncve.org →this looks wrong →
Record history
7 dated edit eventsPublished
- 32 products named later, not at publication
28 days between eventsProducts addedSource 9f70c2d — commit 9f70c2dd609c in the CVE catalog
- not namedsimatic wincc oa v3.17, simatic wincc oa v3.18and 1 more
35 days between eventsProducts addedSource a6a8aa8 — commit a6a8aa8d3c0c in the CVE catalog
- not namedsimatic braumat, simatic sistar
28 days between eventsProducts addedSource 94a7d7c — commit 94a7d7cf856d in the CVE catalog
- not namedsimatic comfort/mobile rt, simatic ipc diagmonitorand 4 more
63 days between eventsProducts addedSource 9f24b0a — commit 9f24b0a0c245 in the CVE catalog
- not namedsimatic pcs 7 v9.1, simatic wincc opc ua client
28 days between eventsProducts addedSource 94a1480 — commit 94a1480facaa in the CVE catalog
- not namedsimatic wincc runtime professional v16and 6 more
28 days between eventsProducts addedSource 5091e07 — commit 5091e0781cb7 in the CVE catalog
- not namedsimatic net pc software v14, simatic net pc software v16and 2 more
496 days between eventsProducts addedSource b73c8db — commit b73c8db67b69 in the CVE catalog
- not namedsimatic et 200sp cpu 1510sp f-1 pnand 7 more
- 1 changeBefore7.5After8.7stays highAssessments not comparable · published base score
385 days to snapshotSnapshot
Source record: View on CVE.org ↗
Check my CVEs
Add your patched version to compare it with the recorded boundary.
Change cards link to the source commit. Compare CVE values with the first mirrored record and KEV values with the preceding catalog snapshot. Verify one finding yourself →
Data sources and quality
CVE values compare the first mirrored record with later source states. Initial records may have been backfilled after publication. KEV events compare consecutive catalog snapshots. Dates identify the reported value’s first observed appearance; earlier intermediate revisions may exist. Only counted rows contribute to totals. as of the 2026-09-07 snapshot.
1 row marked filtered, not counted is on the rail and counted nowhere. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site.
Not checked: a record published before 2023 cannot have its state at publication recovered, so the CVE-record checks never compared it. For such a record, silence on this page means it was not looked at, not that it held.
Not checked: a CISA KEV listing added before 2025-01-27 was never seen changing, so a record that has been in KEV for years carries no listing node here. A missing KEV node is not evidence that CISA has not listed it.
The GitHub Advisory Database was read and carries no changed advisory naming CVE-2023-28831. An advisory is an entry in the GitHub Advisory Database, the GHSA page a Dependabot alert links to. It is reached from a CVE id only when the advisory names that CVE id itself, and many advisories name none. So no advisory here means none was found among the advisories that name one of these ids. It does not mean there is nothing to find.
How every one of these figures is measured, in full →
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
Shipped snapshot computed 2026-09-07 from catalog commit ed5547afbae2. Real findings, not live ones: records amended since are not reflected. A later fix version is evidence that the record changed, not evidence that the first fix was incomplete.