Skip to content

Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

66 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter
ChangedSourceRows

One change, in full: Product added: 20 products named as affected from siemens. The same change in 16 CVE records, across 20 products: 66 rows in all. Drawn here as 12 lines, one per product. Back to the ledger

Counted changes published by siemens, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.KindRecord, Which record was edited, by its CVE id, or how many records one collapsed line stands on.Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
2024-08-13Product addednot named as affected at publication, now names scalance m812-1 adsl-routerTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44317same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44318same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44319same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44320same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44322same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44373same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44374same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13Product addednot named as affected at publication, now names scalance m816-1 adsl-routerTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44317same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44318same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44319same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44320same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44322same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44373same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44374same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13Product addednot named as affected at publication, now names scalance m876-3Time to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44317same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44318same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44319same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44320same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44322same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44373same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13Product addednot named as affected at publication, now names scalance s615 eec lan-routerTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44317same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44318same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44319same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44320same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44322same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44373same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44374same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13Product addednot named as affected at publication, now names scalance s615 lan-routerTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44317same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44318same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44319same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44320same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44322same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44373same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44374same vendor as the line abovesame change as the line aboveTime to revision 273 days
2024-08-13Product addedCVE-2023-44321not named as affected at publication, now names scalance m812-1 adsl-router family and 10 moreTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44321same vendor as the line abovenot named as affected at publication, now names scalance m812-1 adsl-router familyTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44321same vendor as the line abovenot named as affected at publication, now names scalance m816-1 adsl-router familyTime to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44321same vendor as the line abovenot named as affected at publication, now names scalance m874-3 3g-router (cn)Time to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44321same vendor as the line abovenot named as affected at publication, now names scalance m876-3Time to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44321same vendor as the line abovenot named as affected at publication, now names scalance mum853-1 (a1)Time to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44321same vendor as the line abovenot named as affected at publication, now names scalance mum853-1 (b1)Time to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44321same vendor as the line abovenot named as affected at publication, now names scalance mum856-1 (a1)Time to revision 273 days
2024-08-13same kind of change as the line aboveCVE-2023-44321same vendor as the line abovenot named as affected at publication, now names scalance mum856-1 (b1)Time to revision 273 days
3 more rows in this change are not listed here. Open all 11 rows
2024-08-13Product addedCVE-2023-46280not named as affected at publication, now names sinec nmsTime to revision 91 days
2024-08-13Product addedCVE-2024-32635not named as affected at publication, now names jt2go and 3 moreTime to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32635same vendor as the line abovenot named as affected at publication, now names jt2goTime to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32635same vendor as the line abovenot named as affected at publication, now names teamcenter visualization v14.2Time to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32635same vendor as the line abovenot named as affected at publication, now names teamcenter visualization v14.3Time to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32635same vendor as the line abovenot named as affected at publication, now names teamcenter visualization v2312Time to revision 91 days
2024-08-13Product addedCVE-2024-32636not named as affected at publication, now names jt2go and 3 moreTime to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32636same vendor as the line abovenot named as affected at publication, now names jt2goTime to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32636same vendor as the line abovenot named as affected at publication, now names teamcenter visualization v14.2Time to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32636same vendor as the line abovenot named as affected at publication, now names teamcenter visualization v14.3Time to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32636same vendor as the line abovenot named as affected at publication, now names teamcenter visualization v2312Time to revision 91 days
2024-08-13Product addedCVE-2024-32637not named as affected at publication, now names jt2go and 3 moreTime to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32637same vendor as the line abovenot named as affected at publication, now names jt2goTime to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32637same vendor as the line abovenot named as affected at publication, now names teamcenter visualization v14.2Time to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32637same vendor as the line abovenot named as affected at publication, now names teamcenter visualization v14.3Time to revision 91 days
2024-08-13same kind of change as the line aboveCVE-2024-32637same vendor as the line abovenot named as affected at publication, now names teamcenter visualization v2312Time to revision 91 days
2024-08-13Product addednot named as affected at publication, now names omnivise t3000 r8.2 sp3Time to revision 11 days
2024-08-13same kind of change as the line aboveCVE-2024-38876same vendor as the line abovesame change as the line aboveTime to revision 11 days
2024-08-13same kind of change as the line aboveCVE-2024-38877same vendor as the line abovesame change as the line aboveTime to revision 11 days
2024-08-13same kind of change as the line aboveCVE-2024-38878same vendor as the line abovesame change as the line aboveTime to revision 11 days
2024-08-13same kind of change as the line aboveCVE-2024-38879same vendor as the line abovesame change as the line aboveTime to revision 11 days
2024-08-13Product addednot named as affected at publication, now names omnivise t3000 r8.2 sp4Time to revision 11 days
2024-08-13same kind of change as the line aboveCVE-2024-38876same vendor as the line abovesame change as the line aboveTime to revision 11 days
2024-08-13same kind of change as the line aboveCVE-2024-38877same vendor as the line abovesame change as the line aboveTime to revision 11 days
2024-08-13same kind of change as the line aboveCVE-2024-38878same vendor as the line abovesame change as the line aboveTime to revision 11 days
2024-08-13same kind of change as the line aboveCVE-2024-38879same vendor as the line abovesame change as the line aboveTime to revision 11 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

What this page cannot see

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

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.

The units, the refusals, the cut-offs and every source, in full →

Paste your closed CVE tickets and see which of these changes hit them →