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

Counted changes of "CVSS base score changed" published by VulDB, 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.
Thu 26 Feb 2026· 1 change
2026-02-26	CVE-2024-8411	whole record VulDB	stated at publication 5.3, now states 5.1CVSS v4.0 · base scoreMediumMedium	Time to revision 540 days
Wed 8 Oct 2025· 1 change
2025-10-08	CVE-2025-6763	whole record VulDB	stated at publication 7.7, now states 9.2CVSS v4.0 · base scoreHighCritical	Time to revision 103 days
Mon 1 Sep 2025· 1 change
2025-09-01	CVE-2024-7218	whole record VulDB	stated at publication 5.3, now states 5.1CVSS v4.0 · base scoreMediumMedium	Time to revision 398 days
Thu 17 Jul 2025· 2 changes
2025-07-17	Show all 2 CVE records in this change: CVSS base score changed: 5.3 → 5.1Hide the 2 CVE records in this change: CVSS base score changed: 5.3 → 5.1	whole record VulDB	stated at publication 5.3, now states 5.1CVSS v4.0 · base scoreMediumMedium	Time to revision 397 days
2025-07-17	CVE-2024-6005	same vendor as the line above	same change as the line above	Time to revision 397 days
2025-07-17	CVE-2024-6006	same vendor as the line above	same change as the line above	Time to revision 397 days
Wed 16 Jul 2025· 1 change
2025-07-16	CVE-2025-5874	whole record VulDB	stated at publication 5.5, now states 4.6CVSS v3.1 · base scoreMediumMedium	Time to revision 37 days
Thu 10 Jul 2025· 1 change
2025-07-10	CVE-2024-6344	whole record VulDB	stated at publication 5.1, now states 4.8CVSS v4.0 · base scoreMediumMedium	Time to revision 379 days
Tue 10 Jun 2025· 1 change
2025-06-10	CVE-2024-6807	whole record VulDB	stated at publication 5.1, now states 4.8CVSS v4.0 · base scoreMediumMedium	Time to revision 328 days
Wed 30 Apr 2025· 1 change
2025-04-30	CVE-2024-13080	whole record VulDB	stated at publication 5.3, now states 5.1CVSS v4.0 · base scoreMediumMedium	Time to revision 120 days
Wed 16 Apr 2025· 1 change
2025-04-16	CVE-2025-0721	whole record VulDB	stated at publication 6.9, now states 5.3CVSS v4.0 · base scoreMediumMedium	Time to revision 80 days
Mon 10 Feb 2025· 1 change
2025-02-10	CVE-2025-0961	whole record VulDB	stated at publication 5.3, now states 5.1CVSS v4.0 · base scoreMediumMedium	Time to revision 9 days
Fri 7 Feb 2025· 1 change
2025-02-07	CVE-2025-0869	whole record VulDB	stated at publication 6.9, now states 5.3CVSS v4.0 · base scoreMediumMedium	Time to revision 8 days
Wed 22 Jan 2025· 1 change
2025-01-22	CVE-2024-10761	whole record VulDB	stated at publication 5.3, now states 6.9CVSS v4.0 · base scoreMediumMedium	Time to revision 79 days
Wed 22 Nov 2023· 2 changes
2023-11-22	CVE-2023-1009	whole record VulDB	stated at publication 3.5, now states 6.5CVSS v3.1 · base scoreLowMedium	Time to revision 271 days
2023-11-22	CVE-2023-1163	whole record VulDB	stated at publication 4.3, now states 6.5CVSS v3.1 · base scoreMediumMedium	Time to revision 265 days
Sun 22 Oct 2023· 1 change
2023-10-22	CVE-2023-2091	whole record VulDB	stated at publication 5.3, now states 7.8CVSS v3.1 · base scoreMediumHigh	Time to revision 190 days
Thu 6 Jul 2023· 1 change
2023-07-06	CVE-2023-3529	whole record VulDB	stated at publication 4.3, now states 5.3CVSS v3.1 · base scoreMediumMedium	Time to revision 0 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 →