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.

10 changes behind one line · newest firstCSV JSON RSS

SinceKindSeverityVendorSortClear all

PublisherPublishedChangedSourceRows

One change, in full: CVSS base score changed: 9.8 → 8.8. The same change in 10 CVE records. Back to the ledger

Counted changes of "CVSS base score changed" published by Fluid Attacks, 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.
2025-05-19	CVE-2023-5007	whole record Fluid Attacks	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 516 days
2025-05-19	CVE-2023-5010	whole record Fluid Attacks	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 516 days
2025-05-19	CVE-2023-5011	whole record Fluid Attacks	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 516 days
2025-05-19	CVE-2023-45115	whole record Fluid Attacks	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 515 days
2025-05-19	CVE-2023-45116	whole record Fluid Attacks	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 515 days
2025-05-19	CVE-2023-45117	whole record Fluid Attacks	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 515 days
2025-05-19	CVE-2023-45118	whole record Fluid Attacks	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 515 days
2025-05-19	CVE-2023-45119	whole record Fluid Attacks	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 515 days
2025-05-19	CVE-2023-45120	whole record Fluid Attacks	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 515 days
2025-05-19	CVE-2023-45121	whole record Fluid Attacks	stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh	Time to revision 515 days

This kind is counted once per CVE record, so changes and records are the same number here.

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 →