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.

20 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter

One change, in full: Product added: 6 products named as affected from siemens. The same change in 10 CVE records, across 6 products: 20 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.
2023-11-14Product addedCVE-2023-28831not named as affected at publication, now names simatic braumat and 1 moreTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-28831same vendor as the line abovenot named as affected at publication, now names simatic braumatTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-28831same vendor as the line abovenot named as affected at publication, now names simatic sistarTime to revision 63 days
2023-11-14Product addednot named as affected at publication, now names tecnomatix plant simulation v2201Time to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38070same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38071same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38072same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38073same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38074same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38075same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38076same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14Product addednot named as affected at publication, now names tecnomatix plant simulation v2302Time to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38070same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38071same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38072same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38073same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38074same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38075same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-38076same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14Product addednot named as affected at publication, now names simcenter femap v2301Time to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-41032same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-41033same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14Product addednot named as affected at publication, now names simcenter femap v2306Time to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-41032same vendor as the line abovesame change as the line aboveTime to revision 63 days
2023-11-14same kind of change as the line aboveCVE-2023-41033same vendor as the line abovesame change as the line aboveTime to revision 63 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 →