Every change, newest first

Compare earlier and later source statements, with the dates and evidence behind each measured change.

61 changes · newest first · grouped by dayCSV JSON RSS

SinceKindVendorSortClear all

Showing changes seen on 2026-04-23. Every day

Counted changes changed on 2026-04-23, 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.	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 23 Apr 2026· 61 changes
2026-04-23	Added to CISA KEV	CVE-2026-39987	MarimoMarimo CISA KEV	fix due 2026-05-07	Duration unknown
2026-04-23	Product added	CVE-2026-0834	tp link systems inc. TPLink	not named as affected at publication, now names tl-wr841n v13	Time to revision 92 days
2026-04-23	Product added	CVE-2025-12103	red hat	not named as affected at publication, now names red hat openshift ai 2.25	Time to revision 177 days
2026-04-23	Product added	CVE-2023-45271	wpxpo Patchstack	not named as affected at publication, now names wowstore	Time to revision 476 days
2026-04-23	Product added	CVE-2023-49193	nerdpress Patchstack	not named as affected at publication, now names hubbub lite	Time to revision 500 days
2026-04-23	Product added	CVE-2023-51355	multivendorx Patchstack	not named as affected at publication, now names multivendorx	Time to revision 500 days
2026-04-23	Product added	Show all 3 CVE records in this change: Product added: red hat update infrastructure 5 named as affected from red hatHide the 3 CVE records in this change: Product added: red hat update infrastructure 5 named as affected from red hat	red hat	not named as affected at publication, now names red hat update infrastructure 5	Time to revision 24 to 41 days
2026-04-23	same kind of change as the line above	CVE-2026-4111	same vendor as the line above	same change as the line above	Time to revision 41 days
2026-04-23	same kind of change as the line above	CVE-2026-4424	same vendor as the line above	same change as the line above	Time to revision 35 days
2026-04-23	same kind of change as the line above	CVE-2026-5121	same vendor as the line above	same change as the line above	Time to revision 24 days
2026-04-23	CVSS base score changed	CVE-2024-37555	whole record Patchstack	stated at publication 9.1, now states 9.6CVSS v3.1 · base scoreCriticalCriticalOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 631 days
2026-04-23	CVSS base score changed	CVE-2024-43933	whole record Patchstack	stated at publication 4.3, now states 7.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 517 days
2026-04-23	CVSS base score changed	Show all 5 CVE records in this change: CVSS base score changed: 6.5 → 7.1Hide the 5 CVE records in this change: CVSS base score changed: 6.5 → 7.1	whole record Patchstack	stated at publication 6.5, now states 7.1CVSS v3.1 · base scoreMediumHighBranches and original-value intervals are stated on each row.	Time to revision 224 to 561 days
2026-04-23	same kind of change as the line above	CVE-2024-43938	same vendor as the line above	same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 561 days
2026-04-23	same kind of change as the line above	CVE-2025-49411	same vendor as the line above	same change as the line above	Time to revision 246 days
2026-04-23	same kind of change as the line above	CVE-2025-49420	same vendor as the line above	same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	same kind of change as the line above	CVE-2025-49424	same vendor as the line above	same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	same kind of change as the line above	CVE-2025-49893	same vendor as the line above	same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	CVSS base score changed	CVE-2024-47338	whole record Patchstack	stated at publication 7.6, now states 8.5CVSS v3.1 · base scoreHighHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 542 days
2026-04-23	CVSS base score changed	CVE-2024-47634	whole record Patchstack	stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 528 days
2026-04-23	CVSS base score changed	CVE-2024-49256	whole record Patchstack	stated at publication 5.4, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 516 days
2026-04-23	CVSS base score changed	CVE-2024-50430	whole record Patchstack	stated at publication 5.9, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 498 days
2026-04-23	CVSS base score changed	CVE-2024-50441	whole record Patchstack	stated at publication 7.4, now states 6.5CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 520 days
2026-04-23	CVSS base score changed	CVE-2024-51676	whole record Patchstack	stated at publication 7.1, now states 6.5CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 508 days
2026-04-23	CVSS base score changed	CVE-2025-22704	whole record Patchstack	stated at publication 5.4, now states 7.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 422 days
2026-04-23	CVSS base score changed	CVE-2025-24748	whole record Patchstack	stated at publication 8.5, now states 5.3CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 271 days
2026-04-23	CVSS base score changed	CVE-2025-24757	whole record Patchstack	stated at publication 6.5, now states 5.3CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 271 days
2026-04-23	CVSS base score changed	CVE-2025-25081	whole record Patchstack	stated at publication 4.2, now states 4.8CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 418 days
2026-04-23	CVSS base score changed	CVE-2025-25121	whole record Patchstack	stated at publication 7.1, now states 5.4CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 394 days
2026-04-23	CVSS base score changed	CVE-2025-25162	whole record Patchstack	stated at publication 7.5, now states 7.1CVSS v3.1 · base scoreHighHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 394 days
2026-04-23	CVSS base score changed	CVE-2025-32180	whole record Patchstack	stated at publication 4.3, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 320 days
2026-04-23	CVSS base score changed	CVE-2025-32245	whole record Patchstack	stated at publication 8.5, now states 7.1CVSS v3.1 · base scoreHighHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 320 days
2026-04-23	CVSS base score changed	CVE-2025-32281	whole record Patchstack	stated at publication 9.8, now states 4.3CVSS v3.1 · base scoreCriticalMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 278 days
2026-04-23	CVSS base score changed	CVE-2025-32642	whole record Patchstack	stated at publication 10.0, now states 9.6CVSS v3.1 · base scoreCriticalCriticalOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 357 days
2026-04-23	CVSS base score changed	CVE-2025-39537	whole record Patchstack	stated at publication 5.3, now states 7.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 320 days
2026-04-23	CVSS base score changed	CVE-2025-47444	whole record Patchstack	stated at publication 7.5, now states 5.3CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 232 days
2026-04-23	CVSS base score changed	CVE-2025-49288	whole record Patchstack	stated at publication 4.3, now states 8.8CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 299 days
2026-04-23	CVSS base score changed	Show all 2 CVE records in this change: CVSS base score changed: 6.5 → 9.8Hide the 2 CVE records in this change: CVSS base score changed: 6.5 → 9.8	whole record Patchstack	stated at publication 6.5, now states 9.8CVSS v3.1 · base scoreMediumCriticalBranches and original-value intervals are stated on each row.	Time to revision 224 to 246 days
2026-04-23	same kind of change as the line above	CVE-2025-49400	same vendor as the line above	same change as the line above	Time to revision 246 days
2026-04-23	same kind of change as the line above	CVE-2025-49422	same vendor as the line above	same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	CVSS base score changed	CVE-2025-49402	whole record Patchstack	stated at publication 6.5, now states 8.5CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 216 days
2026-04-23	CVSS base score changed	CVE-2025-49405	whole record Patchstack	stated at publication 8.1, now states 4.3CVSS v3.1 · base scoreHighMedium	Time to revision 238 days
2026-04-23	CVSS base score changed	CVE-2025-49406	whole record Patchstack	stated at publication 5.3, now states 8.5CVSS v3.1 · base scoreMediumHigh	Time to revision 246 days
2026-04-23	CVSS base score changed	CVE-2025-49407	whole record Patchstack	stated at publication 7.1, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 238 days
2026-04-23	CVSS base score changed	CVE-2025-49408	whole record Patchstack	stated at publication 4.9, now states 10.0CVSS v3.1 · base scoreMediumCritical	Time to revision 246 days
2026-04-23	CVSS base score changed	Show all 3 CVE records in this change: CVSS base score changed: 5.9 → 9.8Hide the 3 CVE records in this change: CVSS base score changed: 5.9 → 9.8	whole record Patchstack	stated at publication 5.9, now states 9.8CVSS v3.1 · base scoreMediumCriticalBranches and original-value intervals are stated on each row.	Time to revision 224 to 246 days
2026-04-23	same kind of change as the line above	CVE-2025-49409	same vendor as the line above	same change as the line above	Time to revision 246 days
2026-04-23	same kind of change as the line above	CVE-2025-49434	same vendor as the line above	same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	same kind of change as the line above	CVE-2025-49890	same vendor as the line above	same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	CVSS base score changed	CVE-2025-49410	whole record Patchstack	stated at publication 6.5, now states 10.0CVSS v3.1 · base scoreMediumCritical	Time to revision 246 days
2026-04-23	CVSS base score changed	CVE-2025-49413	whole record Patchstack	stated at publication 5.9, now states 7.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	CVSS base score changed	CVE-2025-49426	whole record Patchstack	stated at publication 4.3, now states 8.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	CVSS base score changed	CVE-2025-49428	whole record Patchstack	stated at publication 5.9, now states 7.5CVSS v3.1 · base scoreMediumHigh	Time to revision 246 days
2026-04-23	CVSS base score changed	CVE-2025-49436	whole record Patchstack	stated at publication 6.5, now states 8.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	CVSS base score changed	CVE-2025-49438	whole record Patchstack	stated at publication 7.2, now states 8.1CVSS v3.1 · base scoreHighHigh	Time to revision 246 days
2026-04-23	CVSS base score changed	CVE-2025-49455	whole record Patchstack	stated at publication 9.8, now states 9.3CVSS v3.1 · base scoreCriticalCriticalOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 295 days
2026-04-23	CVSS base score changed	Show all 3 CVE records in this change: CVSS base score changed: 5.9 → 8.1Hide the 3 CVE records in this change: CVSS base score changed: 5.9 → 8.1	whole record Patchstack	stated at publication 5.9, now states 8.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	same kind of change as the line above	CVE-2025-49889	same vendor as the line above	same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	same kind of change as the line above	CVE-2025-49892	same vendor as the line above	same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	same kind of change as the line above	CVE-2025-49894	same vendor as the line above	same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	CVSS base score changed	CVE-2025-49891	whole record Patchstack	stated at publication 5.9, now states 8.5CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 224 days
2026-04-23	CVSS base score changed	CVE-2025-49895	whole record Patchstack	stated at publication 8.8, now states 6.5CVSS v3.1 · base scoreHighMedium	Time to revision 251 days
2026-04-23	CVSS base score changed	CVE-2025-49896	whole record Patchstack	stated at publication 4.3, now states 5.3CVSS v3.1 · base scoreMediumMedium	Time to revision 246 days
2026-04-23	CVSS base score changed	CVE-2025-49897	whole record Patchstack	stated at publication 8.5, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 251 days
2026-04-23	CVSS base score changed	CVE-2025-49898	whole record Patchstack	stated at publication 5.9, now states 7.6CVSS v3.1 · base scoreMediumHigh	Time to revision 251 days
2026-04-23	CVSS base score changed	CVE-2025-62138	whole record Patchstack	stated at publication 5.3, now states 5.4CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23.	Time to revision 91 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.

4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

Every kind of change

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

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 →