Skip to content

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.

11 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "CVSS base score changed" published by twcert, 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 changedDays 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.
Mon 15 Sep 2025· 1 change
2025-09-15CVE-2025-10265
whole record
twcert
stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHighTime to revision 3 days
Fri 22 Aug 2025· 1 change
2025-08-22CVE-2025-9256
whole record
twcert
stated at publication 8.7, now states 7.1CVSS v4.0 · base scoreHighHighTime to revision 0 days
Tue 8 Apr 2025· 1 change
2025-04-08CVE-2025-3364
whole record
twcert
stated at publication 9.8, now states 6.7CVSS v3.1 · base scoreCriticalMediumTime to revision 0 days
Fri 29 Nov 2024· 1 change
2024-11-29CVE-2024-11980
whole record
twcert
stated at publication 10.0, now states 8.6CVSS v3.1 · base scoreCriticalHighTime to revision 0 days
Mon 4 Nov 2024· 1 change
2024-11-04CVE-2024-10653
whole record
twcert
stated at publication 10.0, now states 7.2CVSS v3.1 · base scoreCriticalHighTime to revision 3 days
Tue 15 Oct 2024· 1 change
2024-10-15CVE-2024-45698
whole record
twcert
stated at publication 8.8, now states 9.8CVSS v3.1 · base scoreHighCriticalTime to revision 29 days
Wed 27 Mar 2024· 4 changes
2024-03-274 commits
whole record
twcert
stated at publication 9.8, now states 7.2CVSS v3.1 · base scoreCriticalHighBranches and original-value intervals are stated on each row.Time to revision 202 to 250 days
2024-03-27CVE-2023-35086same vendor as the line abovesame change as the line aboveTime to revision 250 days
2024-03-27CVE-2023-39239same vendor as the line abovesame change as the line aboveTime to revision 202 days
2024-03-27CVE-2023-39238same vendor as the line abovesame change as the line aboveTime to revision 202 days
2024-03-27CVE-2023-39240same vendor as the line abovesame change as the line aboveTime to revision 202 days
Wed 31 Jan 2024· 1 change
2024-01-31CVE-2023-48387
whole record
twcert
stated at publication 6.1, now states 8.8CVSS v3.1 · base scoreMediumHighTime to revision 47 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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
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 →