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.

54 changes behind one line · newest firstCSVJSONRSS

SinceClear all
ChangedSourceRows

One change, in full: Product added: 54 products named as affected in CVE-2025-36579. Products named as affected in 1 CVE record, across 54 products: 54 rows in all, one per record and product. Back to the ledger

Counted changes from 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.
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 13 5320Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 13 5330Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 14 5420Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 14 5430Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 14 5440Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 14 7420 2-in-1Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 14 7430 2-in-1Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 14 7440 2-in-1Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 14 plus 7420Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 14 plus 7430Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 14 plus 7440Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 15 3511Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 15 3520Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 16 5620Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 16 5630Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 16 5640Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 16 7610Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 16 7620 2-in-1Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 16 7630 2-in-1Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 16 7640 2-in-1Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 16 plus 7620Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 16 plus 7630Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 16 plus 7640Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 24 5420 all-in-oneDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 24 5430 all-in-oneDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 27 7720 all-in-oneDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 27 7730 all-in-oneDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 3020 desktopDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 3020 small desktopDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 3030Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 3030sDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 3910Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 5400/5401Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 5401 aioDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 5410 all-in-oneDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 5510Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 7700 all-in-oneDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names inspiron 7710 all-in-oneDays to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3120Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3140Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3140 2in1Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3320Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3330Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3340Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3410Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3420Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3430Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3440Days to revision 0
2026-04-16Product addedCVE-2025-36579not named as affected at publication, now names latitude 3450Days to revision 0
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

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 →