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.

14 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "CVSS base score changed" published by SolarWinds, 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.
Thu 4 Jan 2024· 1 change
2024-01-04CVE-2023-40058
whole record
SolarWinds
stated at publication 7.6, now states 6.5CVSS v3.1 · base scoreHighMediumTime to revision 14 days
Thu 28 Dec 2023· 3 changes
2023-12-28CVE-2023-40061
whole record
SolarWinds
stated at publication 7.1, now states 8.8CVSS v3.1 · base scoreHighHighTime to revision 57 days
2023-12-28CVE-2023-35185
whole record
SolarWinds
stated at publication 8.8, now states 6.8CVSS v3.1 · base scoreHighMediumTime to revision 70 days
2023-12-28CVE-2023-40053
whole record
SolarWinds
stated at publication 4.6, now states 5.0CVSS v3.1 · base scoreMediumMediumTime to revision 23 days
Thu 14 Sep 2023· 6 changes
2023-09-142 commits
whole record
SolarWinds
stated at publication 6.8, now states 7.2CVSS v3.1 · base scoreMediumHighBranches and original-value intervals are stated on each row.Time to revision 50 days
2023-09-14CVE-2023-33225same vendor as the line abovesame change as the line aboveTime to revision 50 days
2023-09-14CVE-2023-23842same vendor as the line abovesame change as the line aboveTime to revision 50 days
2023-09-14CVE-2023-33229
whole record
SolarWinds
stated at publication 3.1, now states 3.5CVSS v3.1 · base scoreLowLowTime to revision 50 days
2023-09-14
whole record
SolarWinds
stated at publication 6.6, now states 7.2CVSS v3.1 · base scoreMediumHighTime to revision 7 to 35 days
2023-09-14CVE-2023-35179same vendor as the line abovesame change as the line aboveTime to revision 35 days
2023-09-14CVE-2023-40060same vendor as the line abovesame change as the line aboveTime to revision 7 days
2023-09-14CVE-2023-3622
whole record
SolarWinds
stated at publication 4.6, now states 4.3CVSS v3.1 · base scoreMediumMediumTime to revision 50 days
Thu 3 Aug 2023· 4 changes
2023-08-03
whole record
SolarWinds
stated at publication 6.8, now states 7.2CVSS v3.1 · base scoreMediumHighTime to revision 8 days
2023-08-03CVE-2023-23843same vendor as the line abovesame change as the line aboveTime to revision 8 days
2023-08-03CVE-2023-23844same vendor as the line abovesame change as the line aboveTime to revision 8 days
2023-08-03CVE-2023-33224same vendor as the line abovesame change as the line aboveTime to revision 8 days
2023-08-03CVE-2023-33231
whole record
SolarWinds
stated at publication 5.4, now states 6.1CVSS v3.1 · base scoreMediumMediumTime to revision 16 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 →