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. |
|---|---|---|---|---|
| Mon 31 Aug 2026· 1 change | ||||
| 2026-08-31 | CVE-2026-81934 | whole record cisa-cg | stated at publication 9.8, now states 7.5Assessments not comparable · base scoreCriticalHighNot 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 4 days |
| Wed 26 Aug 2026· 1 change | ||||
| 2026-08-26 | CVE-2025-12945 | whole record NETGEAR | stated at publication 1.1, now states 2.4Assessments not comparable · base scoreLowLowNot 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 260 days |
| Mon 24 Aug 2026· 1 change | ||||
| 2026-08-24 | CVE-2026-67340 | whole record VulnCheck | stated at publication 9.8, now states 8.6Assessments not comparable · base scoreCriticalHighNot 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 23 days |
| Tue 18 Aug 2026· 1 change | ||||
| 2026-08-18 | CVE-2026-75936 | whole record AMZN | stated at publication 9.9, now states 8.7Assessments not comparable · base scoreCriticalHighNot 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 0 days |
| Mon 17 Aug 2026· 1 change | ||||
| 2026-08-17 | CVE-2025-7639 | whole record icscert | stated at publication 10.0, now states 7.1Assessments not comparable · base scoreCriticalHighOriginal value first replaced 2026-08-14; this value first seen 2026-08-17.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 0 days |
| Mon 10 Aug 2026· 1 change | ||||
| 2026-08-10 | CVE-2024-21489 | whole record snyk | stated at publication 8.2, now states 8.8Assessments not comparable · base scoreHighHighNot 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 678 days |
| Fri 7 Aug 2026· 5 changes | ||||
| 2026-08-07 | whole record WatchGuard | stated at publication 9.1, now states 9.3Assessments not comparable · base scoreCriticalCriticalnot counted: CVSS version set changed | Time to revision 682 days | |
| 2026-08-07 | CVE-2024-6592 | same vendor as the line above | same change as the line aboveNot 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 682 days |
| 2026-08-07 | CVE-2024-6593 | same vendor as the line above | same change as the line aboveNot 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 682 days |
| 2026-08-07 | CVE-2024-6594 | whole record WatchGuard | stated at publication 7.5, now states 8.7Assessments not comparable · base scoreHighHighNot 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 682 days |
| 2026-08-07 | CVE-2024-8424 | whole record WatchGuard | stated at publication 7.8, now states 8.5Assessments not comparable · base scoreHighHighNot 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 638 days |
| 2026-08-07 | CVE-2024-5974 | whole record WatchGuard | stated at publication 7.2, now states 8.6Assessments not comparable · base scoreHighHighNot 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 760 days |
| Wed 5 Aug 2026· 2 changes | ||||
| 2026-08-05 | CVE-2026-71208 | whole record TuranSec | stated at publication 7.1, now states 6.5Assessments not comparable · base scoreHighMediumNot 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 0 days |
| 2026-08-05 | CVE-2026-49004 | whole record zte | stated at publication 10.0, now states 6.5Assessments not comparable · base scoreCriticalMediumNot 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 0 days |
| Mon 3 Aug 2026· 1 change | ||||
| 2026-08-03 | CVE-2024-21539 | whole record snyk | stated at publication 7.5, now states 8.7Assessments not comparable · base scoreHighHighNot 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 622 days |
| Sun 2 Aug 2026· 1 change | ||||
| 2026-08-02 | CVE-2026-67308 | whole record VulnCheck | stated at publication 10.0, now states 9.3Assessments not comparable · base scoreCriticalCriticalNot 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 1 days |
| Sat 1 Aug 2026· 1 change | ||||
| 2026-08-01 | CVE-2024-21536 | whole record snyk | stated at publication 7.5, now states 8.7Assessments not comparable · base scoreHighHighNot 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 651 days |
| Fri 31 Jul 2026· 1 change | ||||
| 2026-07-31 | CVE-2024-4944 | whole record WatchGuard | stated at publication 7.8, now states 8.6Assessments not comparable · base scoreHighHighOriginal value first replaced 2026-07-29; this value first seen 2026-07-31.Not 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 751 days |
| 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 |
| Tue 28 Jul 2026· 2 changes | ||||
| 2026-07-28 | whole record VulnCheck | stated at publication 7.2, now states 6.3Assessments not comparable · base scoreHighMediumnot counted: CVSS assessments are not comparable | Time to revision 0 days | |
| 2026-07-28 | CVE-2026-66752 | 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 | Time to revision 0 days |
| 2026-07-28 | CVE-2026-67181 | 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 | Time to revision 0 days |
| Tue 21 Jul 2026· 1 change | ||||
| 2026-07-21 | CVE-2026-64877 | whole record tenable | stated at publication 9.6, now states 9.4Assessments not comparable · base scoreCriticalCriticalNot 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 0 days |
| Tue 14 Jul 2026· 2 changes | ||||
| 2026-07-14 | CVE-2024-21529 | whole record snyk | stated at publication 8.2, now states 8.8Assessments not comparable · base scoreHighHighNot 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 671 days |
| 2026-07-14 | CVE-2026-7891 | whole record DIVD | stated at publication 9.3, now states 9.1Assessments not comparable · base scoreCriticalCriticalNot 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 68 days |
| Thu 9 Jul 2026· 6 changes | ||||
| 2026-07-09 | whole record VulDB | stated at publication 6.5, now states 8.6Assessments not comparable · base scoreMediumHighnot counted: CVSS assessments are not comparable | Time to revision 1,168 days | |
| 2026-07-09 | CVE-2023-2373 | 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 | Time to revision 1,168 days |
| 2026-07-09 | CVE-2023-2374 | 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 | Time to revision 1,168 days |
| 2026-07-09 | CVE-2023-2375 | 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 | Time to revision 1,168 days |
| 2026-07-09 | CVE-2023-2376 | 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 | Time to revision 1,168 days |
| 2026-07-09 | CVE-2023-2377 | 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 | Time to revision 1,168 days |
| 2026-07-09 | CVE-2023-2378 | 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 | Time to revision 1,168 days |
| Tue 7 Jul 2026· 1 change | ||||
| 2026-07-07 | CVE-2026-3823 | whole record twcert | stated at publication 9.3, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot 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 120 days |
| Thu 2 Jul 2026· 1 change | ||||
| 2026-07-02 | CVE-2024-21527 | whole record snyk | stated at publication 8.2, now states 8.8Assessments not comparable · base scoreHighHighNot 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 714 days |
| Thu 25 Jun 2026· 1 change | ||||
| 2026-06-25 | CVE-2026-56115 | whole record VulnCheck | stated at publication 6.0, now states 8.8Assessments 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 | Time to revision 2 days |
| Tue 23 Jun 2026· 1 change | ||||
| 2026-06-23 | CVE-2026-56784 | whole record VulnCheck | stated at publication 8.3, now states 8.6Assessments 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 | Time to revision 0 days |
| Thu 4 Jun 2026· 4 changes | ||||
| 2026-06-04 | CVE-2026-6074 | whole record icscert | 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 | Time to revision 42 days |
| 2026-06-04 | whole record icscert | stated at publication 7.3, now states 7.8Assessments not comparable · base scoreHighHighnot counted: CVSS version set changed | Time to revision 23 to 175 days | |
| 2026-06-04 | CVE-2025-12659 | same vendor as the line above | same change as the line aboveNot 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 23 days |
| 2026-06-04 | CVE-2025-66585 | same vendor as the line above | same change as the line aboveNot 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 175 days |
| 2026-06-04 | CVE-2025-66586 | same vendor as the line above | same change as the line aboveNot 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 175 days |
| Thu 28 May 2026· 9 changes | ||||
| 2026-05-28 | whole record VulnCheck | stated at publication 4.3, now states 5.3Assessments not comparable · base scoreMediumMediumnot counted: CVSS version set changed | Time to revision 13 days | |
| 2026-05-28 | CVE-2026-45007 | same vendor as the line above | same change as the line aboveNot 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 13 days |
| 2026-05-28 | CVE-2026-45009 | same vendor as the line above | same change as the line aboveNot 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 13 days |
| 2026-05-28 | CVE-2026-45008 | whole record VulnCheck | stated at publication 6.5, now states 7.0Assessments not comparable · base scoreMediumHighNot 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 13 days |
| 2026-05-28 | CVE-2026-45010 | whole record VulnCheck | stated at publication 9.1, 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 | Time to revision 13 days |
| 2026-05-28 | CVE-2026-46359 | whole record VulnCheck | stated at publication 7.5, now states 7.7Assessments not comparable · base scoreHighHighNot 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 13 days |
| 2026-05-28 | CVE-2026-46361 | whole record VulnCheck | stated at publication 6.9, now states 8.2Assessments not comparable · base scoreMediumHighNot 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 13 days |
| 2026-05-28 | CVE-2026-46362 | whole record VulnCheck | stated at publication 6.5, now states 7.1Assessments not comparable · base scoreMediumHighNot 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 13 days |
| 2026-05-28 | CVE-2026-46366 | whole record VulnCheck | stated at publication 7.5, now states 8.7Assessments not comparable · base scoreHighHighNot 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 13 days |
| 2026-05-28 | CVE-2026-46367 | whole record VulnCheck | stated at publication 7.6, now states 8.3Assessments not comparable · base scoreHighHighNot 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 13 days |
| Tue 26 May 2026· 1 change | ||||
| 2026-05-26 | CVE-2026-41948 | whole record VulnCheck | stated at publication 9.2, now states 9.4Assessments not comparable · base scoreCriticalCriticalNot 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 8 days |
| Wed 20 May 2026· 2 changes | ||||
| 2026-05-20 | CVE-2026-47107 | whole record VulnCheck | stated at publication 9.6, now states 8.6Assessments not comparable · base scoreCriticalHighNot 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 1 days |
| 2026-05-20 | CVE-2026-20994 | whole record SamsungMobile | stated at publication 7.0, now states 6.9Assessments not comparable · base scoreHighMediumNot 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 65 days |
| Wed 13 May 2026· 2 changes | ||||
| 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 |
| 2026-05-13 | CVE-2026-8053 | whole record mongodb | stated at publication 8.7, now states 8.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 | Time to revision 0 days |
| Tue 12 May 2026· 2 changes | ||||
| 2026-05-12 | CVE-2025-15617 | whole record VulnCheck | 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 | Time to revision 46 days |
| 2026-05-12 | CVE-2025-15620 | whole record VulnCheck | stated at publication 9.3, now states 9.2Assessments not comparable · base scoreCriticalCriticalNot 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 40 days |
| Fri 1 May 2026· 1 change | ||||
| 2026-05-01 | CVE-2026-41226 | whole record jpcert | stated at publication 6.1, now states 5.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 | Time to revision 1 days |
| Thu 30 Apr 2026· 1 change | ||||
| 2026-04-30 | CVE-2026-3861 | whole record LY-Corporation | stated at publication 6.5, now states 7.1Assessments not comparable · base scoreMediumHighNot 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 14 days |
| Wed 29 Apr 2026· 1 change | ||||
| 2026-04-29 | CVE-2026-41446 | whole record VulnCheck | stated at publication 9.2, 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 | Time to revision 1 days |
| Mon 27 Apr 2026· 1 change | ||||
| 2026-04-27 | CVE-2026-3008 | whole record CSA | stated at publication 10.0, now states 6.6Assessments not comparable · base scoreCriticalMediumNot 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 0 days |
| Fri 24 Apr 2026· 1 change | ||||
| 2026-04-24 | CVE-2026-6349 | whole record twcert | stated at publication 10.0, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot 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 8 days |
| Thu 23 Apr 2026· 2 changes | ||||
| 2026-04-23 | CVE-2026-41461 | whole record VulnCheck | stated at publication 6.3, now states 8.5Assessments not comparable · base scoreMediumHighNot 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 0 days |
| 2026-04-23 | CVE-2026-41460 | whole record VulnCheck | 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 | Time to revision 0 days |
| Wed 22 Apr 2026· 4 changes | ||||
| 2026-04-22 | CVE-2026-22191 | whole record VulnCheck | stated at publication 6.9, now states 5.2Assessments 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 | Time to revision 41 days |
| 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 |
| 2026-04-22 | CVE-2026-41469 | whole record VulnCheck | stated at publication 5.1, now states 5.2Assessments 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 | Time to revision 0 days |
| 2026-04-22 | CVE-2026-22199 | whole record VulnCheck | stated at publication 6.9, now states 8.7Assessments 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 | Time to revision 41 days |
| Mon 20 Apr 2026· 1 change | ||||
| 2026-04-20 | CVE-2026-23758 | whole record VulnCheck | stated at publication 5.1, now states 6.4Assessments 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 | Time to revision 0 days |
| Thu 16 Apr 2026· 1 change | ||||
| 2026-04-16 | CVE-2025-61594 | whole record GitHub_M | stated at publication 2.7, now states 2.1Assessments not comparable · base scoreLowLowNot 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 107 days |
| Wed 15 Apr 2026· 2 changes | ||||
| 2026-04-15 | CVE-2026-34940 | whole record GitHub_M | stated at publication 0.0, now states 8.7Assessments not comparable · base scoreNoneHighNot 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 9 days |
| 2026-04-15 | CVE-2026-32236 | whole record GitHub_M | stated at publication 0.0, now states 1.7Assessments not comparable · base scoreNoneLowNot 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 |
| Mon 13 Apr 2026· 1 change | ||||
| 2026-04-13 | CVE-2026-26221 | whole record VulnCheck | stated at publication 10.0, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot 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 59 days |
| Thu 9 Apr 2026· 2 changes | ||||
| 2026-04-09 | whole record GitHub_M | stated at publication 1.7, now states 8.6Assessments not comparable · base scoreLowHighnot counted: CVSS version set changed | Time to revision 65 days | |
| 2026-04-09 | CVE-2025-62599 | same vendor as the line above | same change as the line aboveNot 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 65 days |
| 2026-04-09 | CVE-2025-62600 | same vendor as the line above | same change as the line aboveNot 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 65 days |
| Wed 8 Apr 2026· 1 change | ||||
| 2026-04-08 | CVE-2026-40035 | whole record VulnCheck | stated at publication 9.8, now states 9.3Assessments not comparable · base scoreCriticalCriticalNot 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 0 days |
| Mon 6 Apr 2026· 2 changes | ||||
| 2026-04-06 | CVE-2026-33579 | whole record VulnCheck | stated at publication 9.8, now states 9.9Assessments not comparable · base scoreCriticalCriticalOriginal value first replaced 2026-03-31; this value first seen 2026-04-06.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 0 days |
| 2026-04-06 | CVE-2026-34570 | whole record GitHub_M | stated at publication 10.0, now states 8.8Assessments 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 | Time to revision 5 days |
| Fri 3 Apr 2026· 1 change | ||||
| 2026-04-03 | CVE-2026-22664 | whole record VulnCheck | stated at publication 7.1, now states 7.7Assessments not comparable · base scoreHighHighNot 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 0 days |
| Thu 2 Apr 2026· 1 change | ||||
| 2026-04-02 | CVE-2023-53908 | whole record VulnCheck | stated at publication 8.7, now states 8.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 | Time to revision 106 days |
| Wed 1 Apr 2026· 6 changes | ||||
| 2026-04-01 | CVE-2026-29014 | whole record VulnCheck | 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 | Time to revision 0 days |
| 2026-04-01 | CVE-2026-34430 | whole record VulnCheck | stated at publication 8.6, now states 8.8Assessments not comparable · base scoreHighHighNot 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 0 days |
| 2026-04-01 | whole record VulnCheck | stated at publication 8.5, now states 7.8Assessments not comparable · base scoreHighHighnot counted: CVSS version set changed | Time to revision 27 days | |
| 2026-04-01 | CVE-2026-27748 | same vendor as the line above | same change as the line aboveNot 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 27 days |
| 2026-04-01 | CVE-2026-27749 | same vendor as the line above | same change as the line aboveNot 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 27 days |
| 2026-04-01 | CVE-2026-27750 | same vendor as the line above | same change as the line aboveNot 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 27 days |
| 2026-04-01 | CVE-2026-35056 | whole record VulnCheck | stated at publication 8.8, now states 8.6Assessments 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 | Time to revision 1 days |
| Tue 31 Mar 2026· 9 changes | ||||
| 2026-03-31 | CVE-2026-32916 | whole record VulnCheck | stated at publication 9.2, now states 9.4Assessments not comparable · base scoreCriticalCriticalNot 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 0 days |
| 2026-03-312 commits | whole record VulnCheck | stated at publication 9.8, now states 8.6Assessments not comparable · base scoreCriticalHighBranches and original-value intervals are stated on each row.not counted: CVSS assessments are not comparable | Time to revision 0 days | |
| 2026-03-31 | CVE-2026-32920 | 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 | Time to revision 0 days |
| 2026-03-31 | CVE-2026-33577 | 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 | Time to revision 0 days |
| 2026-03-312 commits | whole record VulnCheck | stated at publication 9.8, now states 6.9Assessments not comparable · base scoreCriticalMediumBranches and original-value intervals are stated on each row.not counted: CVSS assessments are not comparable | Time to revision 0 days | |
| 2026-03-31 | CVE-2026-34505 | 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 | Time to revision 0 days |
| 2026-03-31 | CVE-2026-33576 | 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 | Time to revision 0 days |
| 2026-03-31 | CVE-2026-34506 | whole record VulnCheck | stated at publication 7.5, now states 4.3Assessments not comparable · base scoreHighMediumNot 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 0 days |
| 2026-03-31 | CVE-2026-33578 | whole record VulnCheck | stated at publication 9.8, now states 5.3Assessments not comparable · base scoreCriticalMediumNot 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 0 days |
| 2026-03-31 | CVE-2026-33580 | whole record VulnCheck | stated at publication 9.8, now states 6.5Assessments not comparable · base scoreCriticalMediumNot 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 0 days |
| 2026-03-31 | CVE-2026-34504 | whole record VulnCheck | stated at publication 6.9, 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 | Time to revision 0 days |
| Fri 27 Mar 2026· 3 changes | ||||
| 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 |
| 2026-03-27 | CVE-2026-32857 | whole record VulnCheck | stated at publication 7.8, now states 8.6Assessments not comparable · base scoreHighHighNot 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 |
| 2026-03-27 | CVE-2026-32859 | whole record VulnCheck | stated at publication 5.1, now states 5.4Assessments 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 | Time to revision 0 days |
| Wed 25 Mar 2026· 16 changes | ||||
| 2026-03-25 | whole record VulnCheck | stated at publication 6.3, now states 6.5Assessments not comparable · base scoreMediumMediumnot counted: CVSS assessments are not comparable | Time to revision 6 to 8 days | |
| 2026-03-25 | CVE-2026-22170 | 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 | Time to revision 8 days |
| 2026-03-25 | CVE-2026-28449 | 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 | Time to revision 7 days |
| 2026-03-25 | CVE-2026-32021 | 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 | Time to revision 6 days |
| 2026-03-25 | CVE-2026-22174 | whole record VulnCheck | stated at publication 5.9, now states 6.8Assessments 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 | Time to revision 8 days |
| 2026-03-25 | whole record VulnCheck | stated at publication 5.8, now states 6.1Assessments not comparable · base scoreMediumMediumnot counted: CVSS assessments are not comparable | Time to revision 2 to 8 days | |
| 2026-03-25 | CVE-2026-22217 | 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 | Time to revision 8 days |
| 2026-03-25 | CVE-2026-27646 | 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 | Time to revision 2 days |
| 2026-03-25 | whole record VulnCheck | stated at publication 6.0, now states 7.1Assessments not comparable · base scoreMediumHighnot counted: CVSS assessments are not comparable | Time to revision 5 to 7 days | |
| 2026-03-25 | CVE-2026-28460 | 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 | Time to revision 7 days |
| 2026-03-25 | CVE-2026-32017 | 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 | Time to revision 6 days |
| 2026-03-25 | CVE-2026-32023 | 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 | Time to revision 6 days |
| 2026-03-25 | CVE-2026-32057 | 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 | Time to revision 5 days |
| 2026-03-25 | CVE-2026-31998 | whole record VulnCheck | stated at publication 8.3, now states 8.6Assessments 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 | Time to revision 7 days |
| 2026-03-25 | whole record VulnCheck | stated at publication 7.3, now states 7.8Assessments not comparable · base scoreHighHighnot counted: CVSS assessments are not comparable | Time to revision 6 days | |
| 2026-03-25 | CVE-2026-32015 | 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 | Time to revision 6 days |
| 2026-03-25 | CVE-2026-32016 | 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 | Time to revision 6 days |
| 2026-03-25 | CVE-2026-32032 | 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 | Time to revision 6 days |
| 2026-03-25 | whole record VulnCheck | stated at publication 6.0, now states 6.5Assessments not comparable · base scoreMediumMediumnot counted: CVSS assessments are not comparable | Time to revision 6 days | |
| 2026-03-25 | CVE-2026-32022 | 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 | Time to revision 6 days |
| 2026-03-25 | CVE-2026-32033 | 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 | Time to revision 6 days |
| Mon 23 Mar 2026· 1 change | ||||
| 2026-03-23 | CVE-2026-32845 | whole record VulnCheck | stated at publication 6.9, now states 8.4Assessments not comparable · base scoreMediumHighNot 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 0 days |
| Fri 20 Mar 2026· 1 change | ||||
| 2026-03-20 | CVE-2026-32844 | whole record VulnCheck | stated at publication 5.1, now states 6.1Assessments 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 | Time to revision 0 days |
| Tue 17 Mar 2026· 4 changes | ||||
| 2026-03-172 commits | whole record VulnCheck | stated at publication 5.1, now states 5.4Assessments not comparable · base scoreMediumMediumBranches and original-value intervals are stated on each row.not counted: CVSS version set changed | Time to revision 0 to 1 days | |
| 2026-03-17 | CVE-2026-32840 | same vendor as the line above | same change as the line aboveNot 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 0 days |
| 2026-03-17 | CVE-2026-29510 | same vendor as the line above | same change as the line aboveNot 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 |
| 2026-03-17 | CVE-2026-29513 | same vendor as the line above | same change as the line aboveNot 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 |
| 2026-03-17 | CVE-2026-29520 | whole record VulnCheck | stated at publication 5.1, now states 6.1Assessments 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 | Time to revision 1 days |
| Tue 10 Mar 2026· 1 change | ||||
| 2026-03-10 | CVE-2026-3843 | whole record TuranSec | stated at publication 10.0, 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 | Time to revision 0 days |
| Fri 6 Mar 2026· 14 changes | ||||
| 2026-03-06 | CVE-2026-28472 | whole record VulnCheck | stated at publication 9.8, now states 9.2Assessments not comparable · base scoreCriticalCriticalNot 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 1 days |
| 2026-03-06 | CVE-2026-28473 | whole record VulnCheck | stated at publication 9.8, now states 8.1Assessments not comparable · base scoreCriticalHighNot 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 1 days |
| 2026-03-062 commits | whole record VulnCheck | stated at publication 6.3, now states 8.3Assessments not comparable · base scoreMediumHighBranches and original-value intervals are stated on each row.not counted: CVSS assessments are not comparable | Time to revision 1 days | |
| 2026-03-06 | CVE-2026-28476 | 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 | Time to revision 1 days |
| 2026-03-06 | CVE-2026-28451 | 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 | Time to revision 1 days |
| 2026-03-06 | CVE-2026-28477 | whole record VulnCheck | stated at publication 7.5, now states 7.1Assessments not comparable · base scoreHighHighOriginal value first replaced 2026-03-05; this value first seen 2026-03-06.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 0 days |
| 2026-03-06 | CVE-2026-28481 | whole record VulnCheck | stated at publication 7.5, now states 6.5Assessments not comparable · base scoreHighMediumOriginal value first replaced 2026-03-05; this value first seen 2026-03-06.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 0 days |
| 2026-03-062 commits | whole record VulnCheck | stated at publication 9.8, now states 6.5Assessments not comparable · base scoreCriticalMediumOriginal value first replaced 2026-03-05; this value first seen 2026-03-06.not counted: CVSS assessments are not comparable | Time to revision 0 days | |
| 2026-03-06 | CVE-2026-29606 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2026-03-05; this value first seen 2026-03-06.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 0 days |
| 2026-03-06 | CVE-2026-28395 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2026-03-05; this value first seen 2026-03-06.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 0 days |
| 2026-03-06 | CVE-2026-29610 | whole record VulnCheck | stated at publication 7.8, now states 8.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 | Time to revision 1 days |
| 2026-03-06 | whole record VulnCheck | stated at publication 9.8, now states 8.2Assessments not comparable · base scoreCriticalHighnot counted: CVSS assessments are not comparable | Time to revision 1 days | |
| 2026-03-06 | CVE-2026-28392 | 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 | Time to revision 1 days |
| 2026-03-06 | CVE-2026-28454 | 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 | Time to revision 1 days |
| 2026-03-06 | CVE-2026-28464 | 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 | Time to revision 1 days |
| 2026-03-06 | CVE-2026-28469 | 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 | Time to revision 1 days |
| 2026-03-06 | CVE-2026-28446 | whole record VulnCheck | stated at publication 9.8, now states 9.4Assessments not comparable · base scoreCriticalCriticalNot 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 1 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 →