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. |
|---|---|---|---|---|
| Wed 29 Jul 2026· 1 change | ||||
| 2026-07-29 | CVE-2024-21537 | whole record snyk | stated at publication 8.8, now states 9.3Assessments not comparable · base scoreHighCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 636 days |
| Wed 13 May 2026· 1 change | ||||
| 2026-05-13 | CVE-2026-44112 | whole record VulnCheck | stated at publication 6.0, now states 9.6Assessments 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 | Time to revision 7 days |
| Wed 22 Apr 2026· 1 change | ||||
| 2026-04-22 | CVE-2026-22192 | whole record VulnCheck | stated at publication 6.3, now states 9.9Assessments 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 | Time to revision 41 days |
| Fri 27 Mar 2026· 1 change | ||||
| 2026-03-27 | CVE-2025-53521 | whole record f5 | stated at publication 8.7, now states 9.8Assessments not comparable · base scoreHighCriticalNot 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 | Time to revision 163 days |
| Mon 2 Mar 2026· 1 change | ||||
| 2026-03-02 | CVE-2026-26338 | whole record VulnCheck | stated at publication 6.9, now states 9.8Assessments 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 | Time to revision 11 days |
| Fri 27 Feb 2026· 1 change | ||||
| 2026-02-27 | CVE-2026-27510 | whole record VulnCheck | stated at publication 6.4, now states 9.6Assessments not comparable · base scoreMediumCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 1 days |
| Wed 21 Jan 2026· 1 change | ||||
| 2026-01-21 | CVE-2025-15113 | whole record VulnCheck | stated at publication 8.5, now states 9.3Assessments not comparable · base scoreHighCriticalNot 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 | Time to revision 22 days |
| Fri 16 Jan 2026· 1 change | ||||
| 2026-01-16 | CVE-2023-53964 | whole record VulnCheck | stated at publication 8.8, now states 9.8Assessments not comparable · base scoreHighCriticalNot 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 | Time to revision 25 days |
| Thu 18 Sep 2025· 1 change | ||||
| 2025-09-18 | CVE-2025-10127 | whole record icscert | stated at publication 8.8, now states 9.8Assessments not comparable · base scoreHighCriticalNot 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 | Time to revision 7 days |
| Thu 4 Sep 2025· 1 change | ||||
| 2025-09-04 | CVE-2025-53187 | whole record ABB | stated at publication 7.3, now states 9.8Assessments not comparable · base scoreHighCriticalOriginal value first replaced 2025-08-21; this value first seen 2025-09-04.Not 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 | Time to revision 10 days |
| Tue 15 Oct 2024· 1 change | ||||
| 2024-10-15 | CVE-2023-22644 | whole record suse | stated at publication 3.8, now states 9.4Assessments not comparable · base scoreLowCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 391 days |
| Fri 11 Oct 2024· 1 change | ||||
| 2024-10-11 | CVE-2023-39363 | whole record GitHub_M | stated at publication 5.9, now states 9.1Assessments not comparable · base scoreMediumCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 431 days |
| Tue 28 May 2024· 1 change | ||||
| 2024-05-28 | CVE-2023-29245 | whole record Nozomi | stated at publication 8.1, now states 9.2Assessments not comparable · base scoreHighCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 252 days |
| Thu 16 May 2024· 1 change | ||||
| 2024-05-16 | CVE-2024-30407 | whole record juniper | stated at publication 8.1, now states 9.2Assessments not comparable · base scoreHighCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 34 days |
| Sun 28 Jan 2024· 1 change | ||||
| 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 | Time to revision 2 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.
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 →