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.

12 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter
ChangedSourceRows

One change, in full: Product added: simcenter femap named as affected from siemens. The same change in 12 CVE records. 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-07-09Product addedCVE-2024-32055not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-32057not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-32058not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-32059not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-32060not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-32061not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-32062not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-32063not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-32064not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-32065not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-32066not named as affected at publication, now names simcenter femapTime to revision 56 days
2024-07-09Product addedCVE-2024-33577not named as affected at publication, now names simcenter femapTime to revision 56 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.

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 →