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.

5 changes · newest first · grouped by dayCSV JSON RSS

SinceKindSeverityVendorSortClear all

PublisherPublishedChangedSourceRows

Counted changes of "CVSS base score changed" published by tenable, 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.
Tue 17 Feb 2026· 1 change
2026-02-17	CVE-2026-2630	whole record tenable	stated at publication 9.9, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 0 days
Wed 4 Sep 2024· 1 change
2024-09-04	CVE-2024-8181	whole record tenable	stated at publication 7.3, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 8 days
Mon 6 May 2024· 1 change
2024-05-06	CVE-2024-4549	whole record tenable	stated at publication 10.0, now states 7.5CVSS v3.1 · base scoreCriticalHigh	Time to revision 0 days
Wed 10 Jan 2024· 2 changes
2024-01-10	CVE-2023-42000	whole record tenable	stated at publication 6.5, now states 9.8CVSS v3.1 · base scoreMediumCritical	Time to revision 44 days
2024-01-10	CVE-2023-41999	whole record tenable	stated at publication 8.3, now states 9.8CVSS v3.1 · base scoreHighCritical	Time to revision 44 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

Every kind of change

All kinds

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

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 →