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.

85 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter

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

Counted changes from 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.
2025-02-11Product addedCVE-2024-50560not named as affected at publication, now names scalance wab762-1 and 16 moreTime to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50560same vendor as the line abovenot named as affected at publication, now names scalance wab762-1Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50560same vendor as the line abovenot named as affected at publication, now names scalance wam763-1Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50560same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (me)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50560same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (us)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50560same vendor as the line abovenot named as affected at publication, now names scalance wam766-1Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50560same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (me)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50560same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (us)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50560same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eecTime to revision 91 days
9 more rows in this change are not listed here. Open all 17 rows
2025-02-11Product addedCVE-2024-50561not named as affected at publication, now names scalance wab762-1 and 16 moreTime to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50561same vendor as the line abovenot named as affected at publication, now names scalance wab762-1Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50561same vendor as the line abovenot named as affected at publication, now names scalance wam763-1Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50561same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (me)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50561same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (us)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50561same vendor as the line abovenot named as affected at publication, now names scalance wam766-1Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50561same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (me)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50561same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (us)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50561same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eecTime to revision 91 days
9 more rows in this change are not listed here. Open all 17 rows
2025-02-11Product addedCVE-2024-50572not named as affected at publication, now names scalance wab762-1 and 16 moreTime to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50572same vendor as the line abovenot named as affected at publication, now names scalance wab762-1Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50572same vendor as the line abovenot named as affected at publication, now names scalance wam763-1Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50572same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (me)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50572same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (us)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50572same vendor as the line abovenot named as affected at publication, now names scalance wam766-1Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50572same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (me)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50572same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (us)Time to revision 91 days
2025-02-11same kind of change as the line aboveCVE-2024-50572same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eecTime to revision 91 days
9 more rows in this change are not listed here. Open all 17 rows
2025-02-11Product addedCVE-2023-44320not named as affected at publication, now names scalance wab762-1 and 16 moreTime to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44320same vendor as the line abovenot named as affected at publication, now names scalance wab762-1Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44320same vendor as the line abovenot named as affected at publication, now names scalance wam763-1Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44320same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (me)Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44320same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (us)Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44320same vendor as the line abovenot named as affected at publication, now names scalance wam766-1Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44320same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (me)Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44320same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (us)Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44320same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eecTime to revision 455 days
9 more rows in this change are not listed here. Open all 17 rows
2025-02-11Product addedCVE-2023-44322not named as affected at publication, now names scalance wab762-1 and 16 moreTime to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44322same vendor as the line abovenot named as affected at publication, now names scalance wab762-1Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44322same vendor as the line abovenot named as affected at publication, now names scalance wam763-1Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44322same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (me)Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44322same vendor as the line abovenot named as affected at publication, now names scalance wam763-1 (us)Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44322same vendor as the line abovenot named as affected at publication, now names scalance wam766-1Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44322same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (me)Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44322same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 (us)Time to revision 455 days
2025-02-11same kind of change as the line aboveCVE-2023-44322same vendor as the line abovenot named as affected at publication, now names scalance wam766-1 eecTime to revision 455 days
9 more rows in this change are not listed here. Open all 17 rows

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 →