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.

18 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter
ChangedSourceRows

One change, in full: Product added: 18 products named as affected in CVE-2024-2637. The same change in 1 CVE record, across 18 products: 18 rows in all. Back to the ledger

Counted changes published by ABB, 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-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names adi .net sdkTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names adi development kitTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names adi driver universalTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names aprolTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names b&r single-touch driverTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names can driverTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names can driver cc770Time to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names can driver sja1000Time to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names hmi service centerTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names hmi service center maintenanceTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names kcf editorTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names serial user mode touch driverTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names sram driverTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names tou0ch lockTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names windows 10 iot enterprise 2019 ltscTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names windows 10 recovery solutionTime to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names windows settings changer (2019 ltsc)Time to revision 345 days
2025-04-24Product addedCVE-2024-2637ABBnot named as affected at publication, now names windows settings changer (ltsc)Time to revision 345 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 →