CVSS base score changed
These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
| 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. |
|---|---|---|---|---|
| Thu 16 May 2024· 3 record changes | ||||
| 2024-05-16 | CVE-2024-30378 | whole record juniper | stated at publication 5.5, now states 6.9Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 30 |
| 2024-05-16 | CVE-2024-4966 | whole record VulDB | stated at publication 6.5, now states 7.5Assessments not comparable · base scoreMediumHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| 2024-05-16 | CVE-2024-4826 | whole record INCIBE | stated at publication 9.3, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 0 |
| Thu 9 May 2024· 1 record change | ||||
| 2024-05-09 | CVE-2024-4645 | whole record VulDB | stated at publication 4.0, now states 5.3Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 1 |
| Mon 6 May 2024· 1 record change | ||||
| 2024-05-06 | CVE-2024-4349 | whole record VulDB | stated at publication 6.5, now states 7.5Assessments not comparable · base scoreMediumHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 6 |
| Thu 18 Apr 2024· 1 record change | ||||
| 2024-04-18 | CVE-2024-1309 | whole record Honeywell | stated at publication 6.4, now states 6.5Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 65 |
| Mon 15 Apr 2024· 1 record change | ||||
| 2024-04-15 | CVE-2024-3764 | whole record VulDB | stated at publication 5.3, now states 3.3Assessments not comparable · base scoreMediumLowNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 0 |
| Sun 28 Jan 2024· 3 record changes | ||||
| 2024-01-28 | whole record VulDB | stated at publication 5.8, now states 8.3Assessments not comparable · base scoreMediumHighnot counted: CVSS assessments are not comparable | Days to revision 2 | |
| 2024-01-28 | CVE-2024-0918 | same vendor as the line above | same change as the line aboveNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 2 |
| 2024-01-28 | CVE-2024-0920 | same vendor as the line above | same change as the line aboveNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 2 |
| 2024-01-28 | CVE-2024-0919 | whole record VulDB | stated at publication 6.5, now states 9.0Assessments not comparable · base scoreMediumCriticalNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 2 |
| Fri 29 Dec 2023· 1 record change | ||||
| 2023-12-29 | CVE-2023-27990 | whole record Zyxel | stated at publication 3.5, now states 4.8Assessments not comparable · base scoreLowMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 249 |
| Thu 30 Nov 2023· 1 record change | ||||
| 2023-11-30 | CVE-2023-6019 | whole record @huntr_ai | stated at publication 10.0, now states 9.8Assessments not comparable · base scoreCriticalCriticalOriginal value first replaced 2023-11-29; this value first seen 2023-11-30.Not counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| Wed 29 Nov 2023· 1 record change | ||||
| 2023-11-29 | CVE-2023-6021 | whole record @huntr_ai | stated at publication 9.3, now states 7.5Assessments not comparable · base scoreCriticalHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 13 |
| Wed 22 Nov 2023· 1 record change | ||||
| 2023-11-22 | CVE-2023-1162 | whole record VulDB | stated at publication 6.5, now states 8.3Assessments not comparable · base scoreMediumHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 265 |
| Thu 2 Nov 2023· 1 record change | ||||
| 2023-11-02 | CVE-2023-1177 | whole record @huntrdev | stated at publication 10.0, now states 9.3Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 224 |
| Wed 4 Oct 2023· 1 record change | ||||
| 2023-10-04 | CVE-2023-22374 | whole record f5 | stated at publication 7.5, now states 8.5Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 244 |
| Thu 3 Aug 2023· 4 record changes | ||||
| 2023-08-03 | CVE-2023-23837 | whole record SolarWinds | stated at publication 4.3, now states 7.5Assessments not comparable · base scoreMediumHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 101 |
| 2023-08-03 | CVE-2023-23838 | whole record SolarWinds | stated at publication 4.0, now states 6.5Assessments not comparable · base scoreMediumMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 101 |
| 2023-08-03 | CVE-2023-23839 | whole record SolarWinds | stated at publication 6.8, now states 6.5Assessments not comparable · base scoreMediumMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 101 |
| 2023-08-03 | CVE-2023-23836 | whole record SolarWinds | stated at publication 8.8, now states 7.2Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 170 |
| Wed 2 Aug 2023· 1 record change | ||||
| 2023-08-02 | CVE-2023-3568 | whole record @huntrdev | stated at publication 4.8, now states 6.3Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Days to revision 23 |
| Wed 12 Jul 2023· 1 record change | ||||
| 2023-07-12 | CVE-2023-20119 | whole record cisco | stated at publication 5.4, now states 6.1Assessments not comparable · base scoreMediumMediumNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 15 |
| Tue 9 May 2023· 1 record change | ||||
| 2023-05-09 | CVE-2023-21738 | whole record microsoft | stated at publication 7.1, now states 7.8Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 120 |
| Thu 27 Apr 2023· 2 record changes | ||||
| 2023-04-27 | CVE-2023-21561 | whole record microsoft | stated at publication 8.8, now states 7.8Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 108 |
| 2023-04-27 | CVE-2023-21779 | whole record microsoft | stated at publication 7.3, now states 7.8Assessments not comparable · base scoreHighHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Days to revision 108 |
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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
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 →