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.

16 changes · newest first · grouped by dayCSV JSON RSS

Counted changes of "CVSS base score changed" published by @huntr_ai, 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 20 Dec 2024· 1 change
2024-12-20	CVE-2024-10101	whole record @huntr_ai	stated at publication 8.2, now states 5.4CVSS v3.0 · base scoreHighMediumOriginal value first replaced 2024-11-04; this value first seen 2024-12-20.	Time to revision 18 days
Mon 4 Nov 2024· 1 change
2024-11-04	CVE-2024-10100	whole record @huntr_ai	stated at publication 7.5, now states 6.5CVSS v3.0 · base scoreHighMedium	Time to revision 18 days
Tue 22 Oct 2024· 1 change
2024-10-22	CVE-2024-10131	whole record @huntr_ai	stated at publication 9.8, now states 8.8CVSS v3.0 · base scoreCriticalHigh	Time to revision 4 days
Mon 15 Jul 2024· 1 change
2024-07-15	CVE-2024-6035	whole record @huntr_ai	stated at publication 9.3, now states 7.4CVSS v3.0 · base scoreCriticalHigh	Time to revision 4 days
Tue 9 Jul 2024· 1 change
2024-07-09	CVE-2024-5389	whole record @huntr_ai	stated at publication 9.3, now states 5.7CVSS v3.0 · base scoreCriticalMedium	Time to revision 30 days
Mon 17 Jun 2024· 1 change
2024-06-17	CVE-2024-5206	whole record @huntr_ai	stated at publication 5.3, now states 4.7CVSS v3.0 · base scoreMediumMedium	Time to revision 11 days
Wed 15 May 2024· 1 change
2024-05-15	CVE-2024-1738	whole record @huntr_ai	stated at publication 9.9, now states 7.5CVSS v3.0 · base scoreCriticalHigh	Time to revision 30 days
Thu 7 Mar 2024· 1 change
2024-03-07	CVE-2024-0759	whole record @huntr_ai	stated at publication 9.6, now states 7.7CVSS v3.0 · base scoreCriticalHigh	Time to revision 10 days
Thu 29 Feb 2024· 1 change
2024-02-29	CVE-2024-1163	whole record @huntr_ai	stated at publication 6.8, now states 7.7CVSS v3.0 · base scoreMediumHigh	Time to revision 16 days
Tue 13 Feb 2024· 1 change
2024-02-13	CVE-2023-6831	whole record @huntr_ai	stated at publication 10.0, now states 8.1CVSS v3.0 · base scoreCriticalHigh	Time to revision 61 days
Thu 8 Feb 2024· 4 changes
2024-02-08	Show all 2 CVE records in this change: CVSS base score changed: 6.7 → 5.4Hide the 2 CVE records in this change: CVSS base score changed: 6.7 → 5.4	whole record @huntr_ai	stated at publication 6.7, now states 5.4CVSS v3.0 · base scoreMediumMediumOriginal value first replaced 2023-12-18; this value first seen 2024-02-08.	Time to revision 2 days
2024-02-08	CVE-2023-6889	same vendor as the line above	same change as the line aboveOriginal value first replaced 2023-12-18; this value first seen 2024-02-08.	Time to revision 2 days
2024-02-08	CVE-2023-6890	same vendor as the line above	same change as the line aboveOriginal value first replaced 2023-12-18; this value first seen 2024-02-08.	Time to revision 2 days
2024-02-08	CVE-2023-6020	whole record @huntr_ai	stated at publication 9.3, now states 7.5CVSS v3.0 · base scoreCriticalHighOriginal value first replaced 2023-11-29; this value first seen 2024-02-08.	Time to revision 13 days
2024-02-08	CVE-2023-6778	whole record @huntr_ai	stated at publication 7.5, now states 5.4CVSS v3.0 · base scoreHighMediumOriginal value first replaced 2023-12-18; this value first seen 2024-02-08.	Time to revision 0 days
Tue 6 Feb 2024· 2 changes
2024-02-06	CVE-2023-6909	whole record @huntr_ai	stated at publication 9.3, now states 7.5CVSS v3.0 · base scoreCriticalHigh	Time to revision 51 days
2024-02-06	CVE-2023-6975	whole record @huntr_ai	stated at publication 10.0, now states 9.8CVSS v3.0 · base scoreCriticalCritical	Time to revision 49 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

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 →