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.

32 changes behind one line · newest firstCSV JSON RSS

SinceKindSeverityVendorSortClear the filter

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

Counted changes of "CVSS base score changed", 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.
2023-10-06	CVE-2023-43728	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43729	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43730	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43731	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43732	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43733	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43734	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43735	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43711	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 7
2023-10-06	CVE-2023-43712	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43713	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43714	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43715	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43716	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43717	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43719	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43720	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43721	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43722	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43723	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43725	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43727	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6
2023-10-06	CVE-2023-43702	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 7
2023-10-06	CVE-2023-43703	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 7
2023-10-06	CVE-2023-43704	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 7
2023-10-06	CVE-2023-43705	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 7
2023-10-06	CVE-2023-43706	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 7
2023-10-06	CVE-2023-43707	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 7
2023-10-06	CVE-2023-43708	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 7
2023-10-06	CVE-2023-43709	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 7
2023-10-06	CVE-2023-43710	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 7
2023-10-06	CVE-2023-5112	whole record Fluid Attacks	stated at publication 8.8, now states 5.4CVSS v3.1 · base scoreHighMedium	Days to revision 6

This kind is counted once per CVE record, so changes and records are the same number here. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.

Data sources and quality

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 →

Check my CVEs against these changes →