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.

90 changes · newest first · grouped by dayCSV JSON RSS

SinceKindSeverityVendorSortClear all

PublisherPublishedChangedSourceRows

Counted changes of "CVSS base score changed" published by microsoft, 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 27 Aug 2026· 1 change
2026-08-27	CVE-2026-65660	whole record microsoft	stated at publication 6.5, now states 8.8CVSS v3.1 · base scoreMediumHigh	Time to revision 16 days
Thu 20 Aug 2026· 2 changes
2026-08-20	Show all 2 CVE records in this change: CVSS base score changed: 8.8 → 9.8Hide the 2 CVE records in this change: CVSS base score changed: 8.8 → 9.8	whole record microsoft	stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 37 days
2026-08-20	CVE-2026-54117	same vendor as the line above	same change as the line above	Time to revision 37 days
2026-08-20	CVE-2026-54118	same vendor as the line above	same change as the line above	Time to revision 37 days
Fri 14 Aug 2026· 1 change
2026-08-14	CVE-2026-65796	whole record microsoft	stated at publication 5.9, now states 8.1CVSS v3.1 · base scoreMediumHigh	Time to revision 3 days
Mon 3 Aug 2026· 2 changes
2026-08-03	CVE-2026-47296	whole record microsoft	stated at publication 7.8, now states 7.5CVSS v3.1 · base scoreHighHigh	Time to revision 20 days
2026-08-03	CVE-2026-55002	whole record microsoft	stated at publication 7.8, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 20 days
Fri 19 Jun 2026· 1 change
2026-06-19	CVE-2026-42915	whole record microsoft	stated at publication 5.7, now states 5.5CVSS v3.1 · base scoreMediumMedium	Time to revision 10 days
Wed 1 Apr 2026· 1 change
2026-04-01	CVE-2026-20963	whole record microsoft	stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 78 days
Mon 23 Mar 2026· 1 change
2026-03-23	CVE-2026-26137	whole record microsoft	stated at publication 8.9, now states 9.9CVSS v3.1 · base scoreHighCritical	Time to revision 4 days
Fri 13 Mar 2026· 2 changes
2026-03-13	Show all 2 CVE records in this change: CVSS base score changed: 8.8 → 8.0Hide the 2 CVE records in this change: CVSS base score changed: 8.8 → 8.0	whole record microsoft	stated at publication 8.8, now states 8.0CVSS v3.1 · base scoreHighHigh	Time to revision 3 days
2026-03-13	CVE-2026-25172	same vendor as the line above	same change as the line above	Time to revision 3 days
2026-03-13	CVE-2026-26111	same vendor as the line above	same change as the line above	Time to revision 3 days
Mon 23 Feb 2026· 1 change
2026-02-23	CVE-2026-21518	whole record microsoft	stated at publication 6.5, now states 8.8CVSS v3.1 · base scoreMediumHigh	Time to revision 13 days
Fri 13 Feb 2026· 1 change
2026-02-13	CVE-2025-59213	whole record microsoft	stated at publication 8.4, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 122 days
Thu 12 Feb 2026· 1 change
2026-02-12	CVE-2026-20841	whole record microsoft	stated at publication 8.8, now states 7.8CVSS v3.1 · base scoreHighHigh	Time to revision 2 days
Wed 11 Feb 2026· 1 change
2026-02-11	CVE-2026-21517	whole record microsoft	stated at publication 7.0, now states 4.7CVSS v3.1 · base scoreHighMedium	Time to revision 0 days
Fri 12 Dec 2025· 1 change
2025-12-12	CVE-2025-62468	whole record microsoft	stated at publication 4.4, now states 5.5CVSS v3.1 · base scoreMediumMedium	Time to revision 3 days
Tue 25 Nov 2025· 1 change
2025-11-25	CVE-2025-64660	whole record microsoft	stated at publication 5.7, now states 8.0CVSS v3.1 · base scoreMediumHigh	Time to revision 5 days
Sat 22 Nov 2025· 3 changes
2025-11-22	Show all 3 CVE records in this change: CVSS base score changed: 6.5 → 9.3Hide the 3 CVE records in this change: CVSS base score changed: 6.5 → 9.3	whole record microsoft	stated at publication 6.5, now states 9.3CVSS v3.1 · base scoreMediumCritical	Time to revision 43 days
2025-11-22	CVE-2025-59252	same vendor as the line above	same change as the line above	Time to revision 43 days
2025-11-22	CVE-2025-59272	same vendor as the line above	same change as the line above	Time to revision 43 days
2025-11-22	CVE-2025-59286	same vendor as the line above	same change as the line above	Time to revision 43 days
Fri 31 Oct 2025· 1 change
2025-10-31	CVE-2025-59503	whole record microsoft	stated at publication 9.9, now states 10.0CVSS v3.1 · base scoreCriticalCritical	Time to revision 8 days
Thu 23 Oct 2025· 1 change
2025-10-23	CVE-2025-55321	whole record microsoft	stated at publication 8.7, now states 9.3CVSS v3.1 · base scoreHighCritical	Time to revision 14 days
Fri 17 Oct 2025· 1 change
2025-10-17	CVE-2025-55320	whole record microsoft	stated at publication 6.7, now states 6.8CVSS v3.1 · base scoreMediumMedium	Time to revision 3 days
Wed 15 Oct 2025· 1 change
2025-10-15	CVE-2025-53132	whole record microsoft	stated at publication 8.0, now states 7.8CVSS v3.1 · base scoreHighHigh	Time to revision 64 days
Thu 18 Sep 2025· 1 change
2025-09-18	CVE-2025-55241	whole record microsoft	stated at publication 9.0, now states 10.0CVSS v3.1 · base scoreCriticalCritical	Time to revision 14 days
Wed 17 Sep 2025· 1 change
2025-09-17	CVE-2025-50154	whole record microsoft	stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium	Time to revision 36 days
Thu 21 Aug 2025· 1 change
2025-08-21	CVE-2025-48807	whole record microsoft	stated at publication 7.5, now states 6.7CVSS v3.1 · base scoreHighMedium	Time to revision 9 days
Tue 22 Jul 2025· 2 changes
2025-07-22	Show all 2 CVE records in this change: CVSS base score changed: 6.3 → 6.5Hide the 2 CVE records in this change: CVSS base score changed: 6.3 → 6.5	whole record microsoft	stated at publication 6.3, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2025-07-21; this value first seen 2025-07-22.	Time to revision 1 to 13 days
2025-07-22	CVE-2025-49706	same vendor as the line above	same change as the line aboveOriginal value first replaced 2025-07-21; this value first seen 2025-07-22.	Time to revision 13 days
2025-07-22	CVE-2025-53771	same vendor as the line above	same change as the line aboveOriginal value first replaced 2025-07-21; this value first seen 2025-07-22.	Time to revision 1 days
Tue 15 Jul 2025· 1 change
2025-07-15	CVE-2025-49716	whole record microsoft	stated at publication 5.9, now states 7.5CVSS v3.1 · base scoreMediumHigh	Time to revision 7 days
Fri 11 Jul 2025· 1 change
2025-07-11	CVE-2025-49670	whole record microsoft	stated at publication 8.8, now states 6.5CVSS v3.1 · base scoreHighMedium	Time to revision 3 days
Tue 8 Jul 2025· 1 change
2025-07-08	CVE-2025-49691	whole record microsoft	stated at publication 8.8, now states 8.0CVSS v3.1 · base scoreHighHigh	Time to revision 0 days
Thu 12 Jun 2025· 1 change
2025-06-12	CVE-2025-47977	whole record microsoft	stated at publication 7.6, now states 8.2CVSS v3.1 · base scoreHighHigh	Time to revision 2 days
Thu 15 May 2025· 1 change
2025-05-15	CVE-2025-29833	whole record microsoft	stated at publication 7.1, now states 7.7CVSS v3.1 · base scoreHighHigh	Time to revision 2 days
Fri 11 Apr 2025· 1 change
2025-04-11	CVE-2025-26647	whole record microsoft	stated at publication 8.1, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 3 days
Thu 3 Apr 2025· 1 change
2025-04-03	CVE-2025-24071	whole record microsoft	stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium	Time to revision 23 days
Thu 6 Feb 2025· 1 change
2025-02-06	CVE-2025-21396	whole record microsoft	stated at publication 7.5, now states 8.2CVSS v3.1 · base scoreHighHigh	Time to revision 8 days
Tue 14 Jan 2025· 2 changes
2025-01-14	Show all 2 CVE records in this change: CVSS base score changed: 7.8 → 8.4Hide the 2 CVE records in this change: CVSS base score changed: 7.8 → 8.4	whole record microsoft	stated at publication 7.8, now states 8.4CVSS v3.1 · base scoreHighHigh	Time to revision 0 days
2025-01-14	CVE-2025-21354	same vendor as the line above	same change as the line above	Time to revision 0 days
2025-01-14	CVE-2025-21362	same vendor as the line above	same change as the line above	Time to revision 0 days
Tue 31 Dec 2024· 1 change
2024-12-31	CVE-2024-38183	whole record microsoft	stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 105 days
Tue 10 Dec 2024· 1 change
2024-12-10	CVE-2023-29348	whole record microsoft	stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHigh	Time to revision 427 days
Thu 14 Nov 2024· 1 change
2024-11-14	CVE-2024-43598	whole record microsoft	stated at publication 7.5, now states 8.1CVSS v3.1 · base scoreHighHigh	Time to revision 2 days
Fri 8 Nov 2024· 1 change
2024-11-08	CVE-2024-43601	whole record microsoft	stated at publication 7.1, now states 7.8CVSS v3.1 · base scoreHighHigh	Time to revision 31 days
Tue 13 Aug 2024· 1 change
2024-08-13	CVE-2024-38200	whole record microsoft	stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium	Time to revision 5 days
Wed 31 Jul 2024· 1 change
2024-07-31	CVE-2024-37973	whole record microsoft	stated at publication 8.4, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 22 days
Fri 19 Jul 2024· 2 changes
2024-07-19	CVE-2024-20652	whole record microsoft	stated at publication 7.5, now states 8.1CVSS v3.1 · base scoreHighHigh	Time to revision 192 days
2024-07-19	CVE-2024-21377	whole record microsoft	stated at publication 7.1, now states 5.5CVSS v3.1 · base scoreHighMedium	Time to revision 157 days
Thu 13 Jun 2024· 1 change
2024-06-13	CVE-2024-30037	whole record microsoft	stated at publication 7.5, now states 5.5CVSS v3.1 · base scoreHighMedium	Time to revision 30 days
Wed 29 May 2024· 1 change
2024-05-29	CVE-2023-35297	whole record microsoft	stated at publication 7.5, now states 8.1CVSS v3.1 · base scoreHighHigh	Time to revision 322 days
Wed 15 May 2024· 1 change
2024-05-15	CVE-2024-30044	whole record microsoft	stated at publication 8.8, now states 7.2CVSS v3.1 · base scoreHighHigh	Time to revision 1 days
Thu 11 Apr 2024· 1 change
2024-04-11	CVE-2024-21378	whole record microsoft	stated at publication 8.0, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 58 days
Wed 14 Feb 2024· 1 change
2024-02-14	CVE-2024-21357	whole record microsoft	stated at publication 7.5, now states 8.1CVSS v3.1 · base scoreHighHigh	Time to revision 1 days
Fri 12 Jan 2024· 1 change
2024-01-12	CVE-2024-20674	whole record microsoft	stated at publication 9.0, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 3 days
Tue 9 Jan 2024· 1 change
2024-01-09	CVE-2023-36719	whole record microsoft	stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh	Time to revision 56 days
Thu 16 Nov 2023· 1 change
2023-11-16	CVE-2023-36423	whole record microsoft	stated at publication 7.2, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 2 days
Thu 9 Nov 2023· 1 change
2023-11-09	CVE-2023-36034	whole record microsoft	stated at publication 6.6, now states 7.3CVSS v3.1 · base scoreMediumHigh	Time to revision 7 days
Mon 6 Nov 2023· 8 changes
2023-11-06	CVE-2023-36420	whole record microsoft	stated at publication 7.3, now states 7.8CVSS v3.1 · base scoreHighHigh	Time to revision 27 days
2023-11-06	CVE-2023-36596	whole record microsoft	stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHigh	Time to revision 27 days
2023-11-06	CVE-2023-36698	whole record microsoft	stated at publication 3.6, now states 4.4CVSS v3.1 · base scoreLowMedium	Time to revision 27 days
2023-11-06	CVE-2023-36761	whole record microsoft	stated at publication 6.2, now states 6.5CVSS v3.1 · base scoreMediumMedium	Time to revision 55 days
2023-11-06	CVE-2023-35391	whole record microsoft	stated at publication 7.1, now states 6.2CVSS v3.1 · base scoreHighMedium	Time to revision 90 days
2023-11-06	CVE-2023-36899	whole record microsoft	stated at publication 7.5, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 90 days
2023-11-06	CVE-2023-36908	whole record microsoft	stated at publication 5.7, now states 6.5CVSS v3.1 · base scoreMediumMedium	Time to revision 90 days
2023-11-06	CVE-2023-38186	whole record microsoft	stated at publication 7.8, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 90 days
Thu 12 Oct 2023· 1 change
2023-10-12	CVE-2023-29338	whole record microsoft	stated at publication 5.0, now states 6.6CVSS v3.1 · base scoreMediumMedium	Time to revision 156 days
Mon 21 Aug 2023· 1 change
2023-08-21	CVE-2023-29360	whole record microsoft	stated at publication 7.8, now states 8.4CVSS v3.1 · base scoreHighHigh	Time to revision 69 days
Tue 8 Aug 2023· 1 change
2023-08-08	CVE-2023-36884	whole record microsoft	stated at publication 0.0, now states 7.5CVSS v3.1 · base scoreNoneHighOriginal value first replaced 2023-07-31; this value first seen 2023-08-08.	Time to revision 20 days
Tue 1 Aug 2023· 6 changes
2023-08-01	CVE-2023-28261	whole record microsoft	stated at publication 6.1, now states 5.7CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2023-06-17; this value first seen 2023-08-01.	Time to revision 50 days
2023-08-01	CVE-2023-24936	whole record microsoft	stated at publication 8.1, now states 7.5CVSS v3.1 · base scoreHighHigh	Time to revision 48 days
2023-08-01	CVE-2023-32012	whole record microsoft	stated at publication 6.3, now states 7.8CVSS v3.1 · base scoreMediumHigh	Time to revision 49 days
2023-08-01	CVE-2023-32013	whole record microsoft	stated at publication 6.5, now states 5.3CVSS v3.1 · base scoreMediumMedium	Time to revision 49 days
2023-08-01	CVE-2023-32020	whole record microsoft	stated at publication 3.7, now states 5.6CVSS v3.1 · base scoreLowMedium	Time to revision 49 days
2023-08-01	CVE-2023-33144	whole record microsoft	stated at publication 5.0, now states 6.6CVSS v3.1 · base scoreMediumMedium	Time to revision 49 days
Fri 14 Jul 2023· 1 change
2023-07-14	CVE-2023-35348	whole record microsoft	stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium	Time to revision 3 days
Sat 17 Jun 2023· 5 changes
2023-06-17	CVE-2023-23416	whole record microsoft	stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh	Time to revision 94 days
2023-06-17	CVE-2023-24856	whole record microsoft	stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHigh	Time to revision 94 days
2023-06-17	CVE-2023-24921	whole record microsoft	stated at publication 4.1, now states 5.4CVSS v3.1 · base scoreMediumMedium	Time to revision 94 days
2023-06-17	CVE-2023-28288	whole record microsoft	stated at publication 6.5, now states 8.1CVSS v3.1 · base scoreMediumHigh	Time to revision 66 days
2023-06-17	CVE-2023-28301	whole record microsoft	stated at publication 4.2, now states 3.7CVSS v3.1 · base scoreMediumLow	Time to revision 66 days
Tue 13 Jun 2023· 1 change
2023-06-13	CVE-2023-24880	whole record microsoft	stated at publication 5.4, now states 4.4CVSS v3.1 · base scoreMediumMedium	Time to revision 91 days
Tue 9 May 2023· 1 change
2023-05-09	CVE-2023-24892	whole record microsoft	stated at publication 7.1, now states 8.2CVSS v3.1 · base scoreHighHigh	Time to revision 56 days
Thu 27 Apr 2023· 3 changes
2023-04-27	CVE-2023-21807	whole record microsoft	stated at publication 5.8, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2023-04-11; this value first seen 2023-04-27.	Time to revision 56 days
2023-04-27	CVE-2023-24858	whole record microsoft	stated at publication 6.5, now states 7.5CVSS v3.1 · base scoreMediumHigh	Time to revision 44 days
2023-04-27	CVE-2023-24911	whole record microsoft	stated at publication 6.5, now states 4.3CVSS v3.1 · base scoreMediumMedium	Time to revision 44 days
Tue 18 Apr 2023· 1 change
2023-04-18	CVE-2023-23379	whole record microsoft	stated at publication 6.4, now states 7.8CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2023-04-14; this value first seen 2023-04-18.	Time to revision 59 days
Fri 14 Apr 2023· 1 change
2023-04-14	CVE-2023-28296	whole record microsoft	stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh	Time to revision 3 days
Tue 11 Apr 2023· 4 changes
2023-04-11	CVE-2023-21722	whole record microsoft	stated at publication 4.4, now states 5.0CVSS v3.1 · base scoreMediumMedium	Time to revision 56 days
2023-04-11	CVE-2023-21778	whole record microsoft	stated at publication 8.3, now states 8.0CVSS v3.1 · base scoreHighHigh	Time to revision 56 days
2023-04-11	Show all 2 CVE records in this change: CVSS base score changed: 8.4 → 7.8Hide the 2 CVE records in this change: CVSS base score changed: 8.4 → 7.8	whole record microsoft	stated at publication 8.4, now states 7.8CVSS v3.1 · base scoreHighHigh	Time to revision 56 days
2023-04-11	CVE-2023-21815	same vendor as the line above	same change as the line above	Time to revision 56 days
2023-04-11	CVE-2023-23381	same vendor as the line above	same change as the line above	Time to revision 56 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 →