Every change, newest first
| 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. | Kind | 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 16 Apr 2026· 5 record changes | |||||
| 2026-04-16 | Product added | CVE-2025-36579 | not named as affected at publication, now names latitude 3510 | Days to revision 0 | |
| 2026-04-16 | Product added | CVE-2025-36579 | not named as affected at publication, now names latitude 3520 | Days to revision 0 | |
| 2026-04-16 | Product added | CVE-2025-36579 | not named as affected at publication, now names latitude 3530 | Days to revision 0 | |
| 2026-04-16 | Product added | CVE-2025-36579 | not named as affected at publication, now names latitude 3540 | Days to revision 0 | |
| 2026-04-16 | Product added | CVE-2025-36579 | not named as affected at publication, now names latitude 3550 | Days to revision 0 | |
| Wed 18 Feb 2026· 1 record change | |||||
| 2026-02-18 | Added to CISA KEV | CVE-2026-22769 | DellRecoverPoint for Virtual Machines (RP4VMs) CISA KEV | fix due 2026-02-21 | Not applicable: Added to CISA KEV has no earlier value |
| Tue 17 Feb 2026· 1 record change | |||||
| 2026-02-17 | Product added | CVE-2025-21120 | not named as affected at publication, now names avamar server | Days to revision 197 | |
| Thu 30 Oct 2025· 1 record change | |||||
| 2025-10-30 | Fix version moved | CVE-2025-43939 | dellunity | stated at publication 5.4, now states 5.5.2Release branch starts at 0.same day | Days to revision 0 |
| Thu 22 Aug 2024· 2 record changes | |||||
| 2024-08-22 | Fix version moved | CVE-2024-0156 | delldell digital delivery (d3) | stated at publication 5.0.86.0, now states 5.2.0.0Release branch starts at 0. | Days to revision 171 |
| 2024-08-22 | Fix version moved | CVE-2024-0155 | delldell digital delivery (d3) | stated at publication 5.0.86.0, now states 5.2.0.0Release branch starts at 0. | Days to revision 171 |
| Wed 3 Jul 2024· 1 record change | |||||
| 2024-07-03 | Product added | CVE-2024-3411 | certcc | not named as affected at publication, now names idrac8 | Days to revision 64 |
Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. 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 →