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.

109 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes from dell, 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.
Fri 3 Jul 2026· 51 changes
2026-07-03Product addedCVE-2026-35159not named as affected at publication, now names precision 3650 mt and 50 moreTime to revision 0 days
2026-07-03same kind of change as the line aboveCVE-2026-35159same vendor as the line abovenot named as affected at publication, now names precision 3650 mtTime to revision 0 days
2026-07-03same kind of change as the line aboveCVE-2026-35159same vendor as the line abovenot named as affected at publication, now names precision 3660Time to revision 0 days
2026-07-03same kind of change as the line aboveCVE-2026-35159same vendor as the line abovenot named as affected at publication, now names precision 3680 towerTime to revision 0 days
2026-07-03same kind of change as the line aboveCVE-2026-35159same vendor as the line abovenot named as affected at publication, now names precision 5470Time to revision 0 days
2026-07-03same kind of change as the line aboveCVE-2026-35159same vendor as the line abovenot named as affected at publication, now names precision 5480Time to revision 0 days
2026-07-03same kind of change as the line aboveCVE-2026-35159same vendor as the line abovenot named as affected at publication, now names precision 5490Time to revision 0 days
2026-07-03same kind of change as the line aboveCVE-2026-35159same vendor as the line abovenot named as affected at publication, now names precision 5560Time to revision 0 days
2026-07-03same kind of change as the line aboveCVE-2026-35159same vendor as the line abovenot named as affected at publication, now names precision 5570Time to revision 0 days
43 more rows in this change are not listed here. Open all 51 rows
Thu 16 Apr 2026· 54 changes
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 13 5320 and 53 moreTime to revision 0 days
2026-04-16same kind of change as the line aboveCVE-2025-36579same vendor as the line abovenot named as affected at publication, now names inspiron 13 5320Time to revision 0 days
2026-04-16same kind of change as the line aboveCVE-2025-36579same vendor as the line abovenot named as affected at publication, now names inspiron 13 5330Time to revision 0 days
2026-04-16same kind of change as the line aboveCVE-2025-36579same vendor as the line abovenot named as affected at publication, now names inspiron 14 5420Time to revision 0 days
2026-04-16same kind of change as the line aboveCVE-2025-36579same vendor as the line abovenot named as affected at publication, now names inspiron 14 5430Time to revision 0 days
2026-04-16same kind of change as the line aboveCVE-2025-36579same vendor as the line abovenot named as affected at publication, now names inspiron 14 5440Time to revision 0 days
2026-04-16same kind of change as the line aboveCVE-2025-36579same vendor as the line abovenot named as affected at publication, now names inspiron 14 7420 2-in-1Time to revision 0 days
2026-04-16same kind of change as the line aboveCVE-2025-36579same vendor as the line abovenot named as affected at publication, now names inspiron 14 7430 2-in-1Time to revision 0 days
2026-04-16same kind of change as the line aboveCVE-2025-36579same vendor as the line abovenot named as affected at publication, now names inspiron 14 7440 2-in-1Time to revision 0 days
46 more rows in this change are not listed here. Open all 54 rows
Tue 17 Feb 2026· 1 change
2026-02-17Product addedCVE-2025-21120not named as affected at publication, now names avamar serverTime to revision 197 days
Thu 30 Oct 2025· 1 change
2025-10-30Fix version movedCVE-2025-43939
dellunity
stated at publication 5.4, now states 5.5.2Release branch starts at 0.same dayTime to revision 0 days
Thu 22 Aug 2024· 2 changes
2024-08-222 commitsFix version moved
delldell digital delivery (d3)
stated at publication 5.0.86.0, now states 5.2.0.0Branches and original-value intervals are stated on each row.Time to revision 171 days
2024-08-22same kind of change as the line aboveCVE-2024-0156same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Time to revision 171 days
2024-08-22same kind of change as the line aboveCVE-2024-0155same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Time to revision 171 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

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 →