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.

14 changes · newest first · grouped by dayCSV JSON RSS

SinceKindSeverityVendorSortClear all

PublisherPublishedChangedSourceRows

Counted changes of "CVSS base score changed" rescored into Critical, published by TR-CERT, 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.
Fri 12 Jun 2026· 1 change
2026-06-12	CVE-2026-11561	whole record TR-CERT	stated at publication 5.3, now states 9.8CVSS v3.1 · base scoreMediumCritical	Time to revision 1 days
Fri 12 Sep 2025· 3 changes
2025-09-12	CVE-2025-2421	whole record TR-CERT	stated at publication 8.2, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 133 days
2025-09-12	CVE-2024-8262	whole record TR-CERT	stated at publication 5.5, now states 9.8CVSS v3.1 · base scoreMediumCriticalOriginal value first replaced 2025-03-10; this value first seen 2025-09-12.	Time to revision 7 days
2025-09-12	CVE-2024-1107	whole record TR-CERT	stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 442 days
Fri 13 Dec 2024· 1 change
2024-12-13	CVE-2024-8259	whole record TR-CERT	stated at publication 6.5, now states 9.8CVSS v3.1 · base scoreMediumCritical	Time to revision 4 days
Wed 27 Nov 2024· 1 change
2024-11-27	CVE-2023-6190	whole record TR-CERT	stated at publication 6.5, now states 9.8CVSS v3.1 · base scoreMediumCritical	Time to revision 336 days
Mon 25 Nov 2024· 1 change
2024-11-25	CVE-2023-4671	whole record TR-CERT	stated at publication 7.5, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 333 days
Thu 27 Jun 2024· 1 change
2024-06-27	CVE-2024-0949	whole record TR-CERT	stated at publication 4.3, now states 9.8CVSS v3.1 · base scoreMediumCritical	Time to revision 0 days
Wed 18 Oct 2023· 1 change
2023-10-18	CVE-2023-4178	whole record TR-CERT	stated at publication 8.2, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 43 days
Wed 26 Jul 2023· 4 changes
2023-07-26	CVE-2023-2884	whole record TR-CERT	stated at publication 6.4, now states 9.8CVSS v3.1 · base scoreMediumCritical	Time to revision 62 days
2023-07-262 commits	Show all 3 CVE records in this change: CVSS base score changed: 8.8 → 9.8Hide the 3 CVE records in this change: CVSS base score changed: 8.8 → 9.8	whole record TR-CERT	stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCriticalBranches and original-value intervals are stated on each row.	Time to revision 9 to 67 days
2023-07-26	CVE-2023-2958	same vendor as the line above	same change as the line above	Time to revision 9 days
2023-07-26	CVE-2023-3048	same vendor as the line above	same change as the line above	Time to revision 43 days
2023-07-26	CVE-2023-2713	same vendor as the line above	same change as the line above	Time to revision 67 days
Thu 6 Apr 2023· 1 change
2023-04-06	CVE-2023-1725	whole record TR-CERT	stated at publication 8.6, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 7 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 →