All changessiemensas of 2026-09-07
CVE-2023-44373
siemensscalance w721-1 rj45cve.org →this looks wrong →
Record history
5 dated edit eventsPublished
- 58 products named later, not at publication
28 days between eventsProducts addedSource 94a7d7c — commit 94a7d7cf856d in the CVE catalog
- not namedruggedcom rm1224 lte(4g) euand 12 more
182 days between eventsProducts addedSource 4698d7d — commit 4698d7d66b8c in the CVE catalog
- not namedscalance wam763-1, scalance wam763-1 (me)and 8 more
63 days between eventsProducts addedSource f753ee9 — commit f753ee9282f5 in the CVE catalog
- not namedscalance m812-1 adsl-router, scalance m816-1 adsl-routerand 3 more
- 1 changeBefore9.1After9.4stays criticalAssessments not comparable · published base score
28 days between eventsProducts addedSource 35a1ed4 — commit 35a1ed475acf in the CVE catalog
- not namedscalance wab762-1, scalance wub762-1
581 days between eventsProducts addedSource 640c50a — commit 640c50a6ec39 in the CVE catalog
- not namedscalance w721-1 rj45, scalance w722-1 rj45and 26 more
146 days to snapshotSnapshot
Source record: View on CVE.org ↗
Check your tickets
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. The full recipe →
Data coverage & methodology
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-44373. 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 f5f9fc6fd7dc. 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.