Product added
| 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. | Record, 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 changed | Days 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. |
|---|---|---|---|---|
| Thu 24 Apr 2025· 18 record changes | ||||
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names adi .net sdk | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names adi development kit | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names adi driver universal | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names aprol | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names b&r single-touch driver | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names can driver | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names can driver cc770 | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names can driver sja1000 | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names hmi service center | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names hmi service center maintenance | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names kcf editor | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names serial user mode touch driver | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names sram driver | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names tou0ch lock | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names windows 10 iot enterprise 2019 ltsc | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names windows 10 recovery solution | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names windows settings changer (2019 ltsc) | Days to revision 345 |
| 2025-04-24 | CVE-2024-2637 | ABB | not named as affected at publication, now names windows settings changer (ltsc) | Days to revision 345 |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.
Data sources and quality
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 →