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.

17 changes · newest first · grouped by dayCSV JSON RSS

SinceKindSeverityVendorSortClear all

PublisherPublishedChangedSourceRows

Showing changes seen on 2025-12-27. Every day

Counted changes of "CVSS base score changed" changed on 2025-12-27, 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.
Sat 27 Dec 2025· 17 changes
2025-12-27	CVE-2023-53905	whole record VulnCheck	stated at publication 8.8, now states 8.0CVSS v3.1 · base scoreHighHigh	Time to revision 10 days
2025-12-27	CVE-2023-53930	whole record VulnCheck	stated at publication 9.8, now states 7.5CVSS v3.1 · base scoreCriticalHigh	Time to revision 10 days
2025-12-27	CVE-2023-53976	whole record VulnCheck	stated at publication 6.4, now states 5.4CVSS v3.1 · base scoreMediumMedium	Time to revision 5 days
2025-12-27	CVE-2023-53977	whole record VulnCheck	stated at publication 6.4, now states 5.4CVSS v3.1 · base scoreMediumMedium	Time to revision 5 days
2025-12-27	CVE-2023-53978	whole record VulnCheck	stated at publication 6.4, now states 5.4CVSS v3.1 · base scoreMediumMedium	Time to revision 5 days
2025-12-27	CVE-2023-53918	whole record VulnCheck	stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium	Time to revision 10 days
2025-12-27	CVE-2023-53925	whole record VulnCheck	stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium	Time to revision 10 days
2025-12-27	CVE-2023-53927	whole record VulnCheck	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Time to revision 10 days
2025-12-27	CVE-2023-53931	whole record VulnCheck	stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium	Time to revision 10 days
2025-12-27	CVE-2023-53953	whole record VulnCheck	stated at publication 6.4, now states 5.4CVSS v3.1 · base scoreMediumMedium	Time to revision 8 days
2025-12-27	CVE-2024-58318	whole record VulnCheck	stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium	Time to revision 9 days
2025-12-27	CVE-2024-58319	whole record VulnCheck	stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMedium	Time to revision 9 days
2025-12-27	CVE-2025-2292	whole record VulnCheck	stated at publication 4.9, now states 6.5CVSS v3.1 · base scoreMediumMedium	Time to revision 271 days
2025-12-27	CVE-2025-2748	whole record VulnCheck	stated at publication 6.5, now states 6.1CVSS v3.1 · base scoreMediumMedium	Time to revision 278 days
2025-12-27	CVE-2025-30004	whole record VulnCheck	stated at publication 9.1, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 271 days
2025-12-27	CVE-2025-30005	whole record VulnCheck	stated at publication 6.7, now states 8.3CVSS v3.1 · base scoreMediumHigh	Time to revision 271 days
2025-12-27	CVE-2025-34509	whole record VulnCheck	stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2025-06-17; this value first seen 2025-12-27.	Time to revision 0 days

This kind is counted once per CVE record, so changes and records are the same number here.

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 →