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.

114 changes · newest first · grouped by dayCSVJSONRSS

SinceClear the filter
ChangedSourceRows
Counted changes published by dell, 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.
Thu 16 Apr 2026· 5 record changes
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3510Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3520Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3530Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3540Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3550Days to revision 0
Tue 17 Feb 2026· 1 record change
2026-02-17Product addedCVE-2025-21120not named as affected at publication, now names avamar serverDays to revision 197
Thu 30 Oct 2025· 1 record change
2025-10-30Fix version movedCVE-2025-43939
dellunity
stated at publication 5.4, now states 5.5.2Release branch starts at 0.same dayDays to revision 0
Thu 12 Jun 2025· 1 record change
2025-06-12CVSS base score changedCVE-2025-32752
whole record
dell
stated at publication 4.9, now states 5.7CVSS v3.1 · base scoreMediumMediumDays to revision 14
Fri 28 Mar 2025· 1 record change
2025-03-28CVSS base score changedCVE-2025-24383
whole record
dell
stated at publication 7.8, now states 9.1CVSS v3.1 · base scoreHighCriticalDays to revision 0
Thu 22 Aug 2024· 2 record changes
2024-08-22Fix version movedCVE-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-22Fix version movedCVE-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
Thu 20 Jul 2023· 1 record change
2023-07-20CVSS base score changedCVE-2023-24568
whole record
dell
stated at publication 7.4, now states 5.0CVSS v3.1 · base scoreHighMediumDays to revision 51
Fri 23 Jun 2023· 1 record change
2023-06-23CVSS base score changedCVE-2023-28043
whole record
dell
stated at publication 6.3, now states 6.5CVSS v3.1 · base scoreMediumMediumDays to revision 22
Wed 14 Jun 2023· 1 record change
2023-06-14CVSS base score changedCVE-2023-28069
whole record
dell
stated at publication 7.1, now states 6.1CVSS v3.1 · base scoreHighMediumDays to revision 70

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 →

Check my CVEs against these changes →