CVSS base score changed

A rescore changes the score, not the flaw: someone restated this record's severity. Nothing here says the vulnerability itself changed.

29 changes · newest first · grouped by dayCSV JSON RSS

SinceKindSeverityVendorSortClear all

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

Counted changes of "CVSS base score changed" changed on 2026-04-28, 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.	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.
Tue 28 Apr 2026· 29 changes
2026-04-28	CVE-2023-25043	whole record Patchstack	stated at publication 5.0, now states 4.3CVSS v3.1 · base scoreMediumMedium	Time to revision 741 days
2026-04-28	Show all 2 CVE records in this change: CVSS base score changed: 7.1 → 5.8Hide the 2 CVE records in this change: CVSS base score changed: 7.1 → 5.8	whole record Patchstack	stated at publication 7.1, now states 5.8CVSS v3.1 · base scoreHighMedium	Time to revision 740 to 972 days
2026-04-28	CVE-2023-25466	same vendor as the line above	same change as the line above	Time to revision 972 days
2026-04-28	CVE-2024-32587	same vendor as the line above	same change as the line above	Time to revision 740 days
2026-04-28	CVE-2023-28418	whole record Patchstack	stated at publication 5.4, now states 7.1CVSS v3.1 · base scoreMediumHigh	Time to revision 1,041 days
2026-04-28	CVE-2023-32123	whole record Patchstack	stated at publication 7.1, now states 6.1CVSS v3.1 · base scoreHighMedium	Time to revision 897 days
2026-04-28	Show all 2 CVE records in this change: CVSS base score changed: 6.5 → 5.4Hide the 2 CVE records in this change: CVSS base score changed: 6.5 → 5.4	whole record Patchstack	stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium	Time to revision 678 to 763 days
2026-04-28	CVE-2023-32237	same vendor as the line above	same change as the line above	Time to revision 763 days
2026-04-28	CVE-2023-35050	same vendor as the line above	same change as the line above	Time to revision 678 days
2026-04-28	CVE-2023-46197	whole record Patchstack	stated at publication 8.8, now states 5.3CVSS v3.1 · base scoreHighMedium	Time to revision 711 days
2026-04-28	CVE-2023-47504	whole record Patchstack	stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium	Time to revision 734 days
2026-04-28	CVE-2023-51405	whole record Patchstack	stated at publication 5.3, now states 8.2CVSS v3.1 · base scoreMediumHigh	Time to revision 734 days
2026-04-28	CVE-2023-51539	whole record Patchstack	stated at publication 4.3, now states 5.4CVSS v3.1 · base scoreMediumMedium	Time to revision 844 days
2026-04-28	CVE-2024-27955	whole record Patchstack	stated at publication 8.3, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 711 days
2026-04-28	Show all 2 CVE records in this change: CVSS base score changed: 6.5 → 5.5Hide the 2 CVE records in this change: CVSS base score changed: 6.5 → 5.5	whole record Patchstack	stated at publication 6.5, now states 5.5CVSS v3.1 · base scoreMediumMedium	Time to revision 726 to 770 days
2026-04-28	CVE-2024-29141	same vendor as the line above	same change as the line above	Time to revision 770 days
2026-04-28	CVE-2024-33948	same vendor as the line above	same change as the line above	Time to revision 726 days
2026-04-28	CVE-2024-29906	whole record Patchstack	stated at publication 6.5, now states 5.9CVSS v3.1 · base scoreMediumMedium	Time to revision 763 days
2026-04-28	CVE-2024-30427	whole record Patchstack	stated at publication 7.1, now states 5.4CVSS v3.1 · base scoreHighMedium	Time to revision 760 days
2026-04-28	CVE-2024-31098	whole record Patchstack	stated at publication 8.1, now states 7.1CVSS v3.1 · base scoreHighHigh	Time to revision 688 days
2026-04-28	Show all 2 CVE records in this change: CVSS base score changed: 7.1 → 5.9Hide the 2 CVE records in this change: CVSS base score changed: 7.1 → 5.9	whole record Patchstack	stated at publication 7.1, now states 5.9CVSS v3.1 · base scoreHighMedium	Time to revision 645 to 740 days
2026-04-28	CVE-2024-32585	same vendor as the line above	same change as the line above	Time to revision 740 days
2026-04-28	CVE-2024-37432	same vendor as the line above	same change as the line above	Time to revision 645 days
2026-04-28	Show all 3 CVE records in this change: CVSS base score changed: 5.9 → 6.5Hide the 3 CVE records in this change: CVSS base score changed: 5.9 → 6.5	whole record Patchstack	stated at publication 5.9, now states 6.5CVSS v3.1 · base scoreMediumMedium	Time to revision 689 to 712 days
2026-04-28	CVE-2024-32800	same vendor as the line above	same change as the line above	Time to revision 712 days
2026-04-28	CVE-2024-34567	same vendor as the line above	same change as the line above	Time to revision 712 days
2026-04-28	CVE-2024-35751	same vendor as the line above	same change as the line above	Time to revision 689 days
2026-04-28	CVE-2024-38728	whole record Patchstack	stated at publication 7.2, now states 7.1CVSS v3.1 · base scoreHighHigh	Time to revision 645 days
2026-04-28	CVE-2024-38739	whole record Patchstack	stated at publication 6.5, now states 5.1CVSS v3.1 · base scoreMediumMedium	Time to revision 648 days
2026-04-28	CVE-2025-24735	whole record Patchstack	stated at publication 5.9, now states 7.7CVSS v3.1 · base scoreMediumHigh	Time to revision 298 days
2026-04-28	CVE-2026-40967	whole record vmware	stated at publication 8.2, now states 8.6CVSS v3.1 · base scoreHighHigh	Time to revision 0 days
2026-04-28	CVE-2026-32589	whole record redhat	stated at publication 7.1, now states 7.4CVSS v3.1 · base scoreHighHigh	Time to revision 20 days
2026-04-28	CVE-2025-54196	whole record adobe	stated at publication 3.1, now states 4.3CVSS v3.1 · base scoreLowMedium	Time to revision 195 days
2026-04-28	CVE-2025-49552	whole record adobe	stated at publication 7.3, now states 8.1CVSS v3.1 · base scoreHighHigh	Time to revision 195 days

This kind is counted once per CVE record, so changes and records are the same number here. 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

All kinds

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 →