CVSS base score changed
| 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 22 Jun 2026· 2 changes | ||||
| 2026-06-22 | CVE-2026-30792 | whole record VULSec | stated at publication 9.1, now states 8.3CVSS v4.0 · base scoreCriticalHigh | Time to revision 109 days |
| 2026-06-22 | CVE-2026-30796 | whole record VULSec | stated at publication 8.7, now states 6.9CVSS v4.0 · base scoreHighMedium | Time to revision 109 days |
| Fri 19 Jun 2026· 5 changes | ||||
| 2026-06-19 | CVE-2026-42915 | whole record microsoft | stated at publication 5.7, now states 5.5CVSS v3.1 · base scoreMediumMedium | Time to revision 10 days |
| 2026-06-19 | CVE-2026-56208 | whole record redhat | stated at publication 8.6, now states 7.6CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| 2026-06-19 | CVE-2026-56209 | whole record redhat | stated at publication 9.1, now states 7.1CVSS v3.1 · base scoreCriticalHigh | Time to revision 0 days |
| 2026-06-19 | CVE-2026-56210 | whole record redhat | stated at publication 8.2, now states 7.1CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| 2026-06-19 | CVE-2026-56211 | whole record redhat | stated at publication 8.1, now states 7.1CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| Thu 18 Jun 2026· 1 change | ||||
| 2026-06-18 | CVE-2026-9591 | whole record Checkmarx | stated at publication 8.3, now states 6.9CVSS v4.0 · base scoreHighMedium | Time to revision 1 days |
| Wed 17 Jun 2026· 10 changes | ||||
| 2026-06-17 | CVE-2026-55202 | whole record VulnCheck | stated at publication 9.3, now states 8.8CVSS v4.0 · base scoreCriticalHigh | Time to revision 0 days |
| 2026-06-17 | CVE-2025-62851 | whole record qnap | stated at publication 6.9, now states 4.6CVSS v4.0 · base scoreMediumMedium | Time to revision 7 days |
| 2026-06-17 | whole record qnap | stated at publication 5.3, now states 1.3CVSS v4.0 · base scoreMediumLow | Time to revision 7 days | |
| 2026-06-17 | CVE-2026-22899 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-06-17 | CVE-2026-24720 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-06-17 | CVE-2026-26240 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-06-17 | CVE-2026-26241 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-06-17 | CVE-2026-24724 | whole record qnap | stated at publication 8.6, now states 6.2CVSS v4.0 · base scoreHighMedium | Time to revision 7 days |
| 2026-06-17 | whole record qnap | stated at publication 8.7, now states 6.6CVSS v4.0 · base scoreHighMedium | Time to revision 7 to 8 days | |
| 2026-06-17 | CVE-2026-26236 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-06-17 | CVE-2026-26237 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-06-17 | CVE-2026-26239 | whole record qnap | stated at publication 8.7, now states 6.3CVSS v4.0 · base scoreHighMedium | Time to revision 7 days |
| Tue 16 Jun 2026· 1 change | ||||
| 2026-06-16 | CVE-2026-6893 | whole record redhat | stated at publication 8.8, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 6 days |
| Fri 12 Jun 2026· 6 changes | ||||
| 2026-06-12 | CVE-2025-10101 | whole record NLOK | stated at publication 8.1, now states 7.8CVSS v3.1 · base scoreHighHigh | Time to revision 193 days |
| 2026-06-12 | CVE-2025-8351 | whole record NLOK | stated at publication 9.0, now states 7.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 193 days |
| 2026-06-12 | CVE-2026-11535 | whole record Vivo | stated at publication 8.7, now states 9.4CVSS v4.0 · base scoreHighCritical | Time to revision 0 days |
| 2026-06-12 | CVE-2026-11561 | whole record TR-CERT | stated at publication 5.3, now states 9.8CVSS v3.1 · base scoreMediumCritical | Time to revision 1 days |
| 2026-06-12 | CVE-2026-45171 | whole record palo_alto | stated at publication 9.3, now states 8.7CVSS v4.0 · base scoreCriticalHigh | Time to revision 0 days |
| 2026-06-12 | CVE-2025-59382 | whole record qnap | stated at publication 5.1, now states 1.2CVSS v4.0 · base scoreMediumLow | Time to revision 2 days |
| Wed 10 Jun 2026· 1 change | ||||
| 2026-06-10 | CVE-2023-42456 | whole record GitHub_M | stated at publication 3.1, now states 3.3CVSS v3.1 · base scoreLowLow | Time to revision 993 days |
| Tue 9 Jun 2026· 7 changes | ||||
| 2026-06-09 | CVE-2026-11429 | whole record Altium | stated at publication 9.4, now states 10.0CVSS v4.0 · base scoreCriticalCritical | Time to revision 4 days |
| 2026-06-092 commits | whole record GitHub_M | stated at publication 8.1, now states 8.0CVSS v3.1 · base scoreHighHighBranches and original-value intervals are stated on each row. | Time to revision 348 days | |
| 2026-06-09 | CVE-2025-52903 | same vendor as the line above | same change as the line above | Time to revision 348 days |
| 2026-06-09 | CVE-2025-52904 | same vendor as the line above | same change as the line above | Time to revision 348 days |
| 2026-06-09 | CVE-2026-10840 | whole record redhat | stated at publication 9.6, now states 7.1CVSS v3.1 · base scoreCriticalHigh | Time to revision 5 days |
| 2026-06-09 | CVE-2025-59381 | whole record qnap | stated at publication 4.6, now states 6.9CVSS v4.0 · base scoreMediumMedium | Time to revision 158 days |
| 2026-06-09 | CVE-2025-66274 | whole record qnap | stated at publication 1.2, now states 5.1CVSS v4.0 · base scoreLowMedium | Time to revision 118 days |
| 2026-06-09 | CVE-2026-22895 | whole record qnap | stated at publication 2.2, now states 6.2CVSS v4.0 · base scoreLowMedium | Time to revision 81 days |
| Fri 5 Jun 2026· 1 change | ||||
| 2026-06-05 | CVE-2026-42250 | whole record CERT-PL | stated at publication 5.1, now states 4.8CVSS v4.0 · base scoreMediumMedium | Time to revision 8 days |
| Thu 4 Jun 2026· 1 change | ||||
| 2026-06-04 | CVE-2025-71316 | whole record cisa-cg | stated at publication 7.8, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 0 days |
| Wed 3 Jun 2026· 10 changes | ||||
| 2026-06-03 | whole record autodesk | stated at publication 7.1, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 132 days | |
| 2026-06-03 | CVE-2026-0533 | same vendor as the line above | same change as the line above | Time to revision 132 days |
| 2026-06-03 | CVE-2026-0534 | same vendor as the line above | same change as the line above | Time to revision 132 days |
| 2026-06-03 | CVE-2026-0535 | same vendor as the line above | same change as the line above | Time to revision 132 days |
| 2026-06-03 | whole record autodesk | stated at publication 7.8, now states 8.4CVSS v3.1 · base scoreHighHigh | Time to revision 119 days | |
| 2026-06-03 | CVE-2026-0537 | same vendor as the line above | same change as the line above | Time to revision 119 days |
| 2026-06-03 | CVE-2026-0538 | same vendor as the line above | same change as the line above | Time to revision 119 days |
| 2026-06-03 | CVE-2026-0660 | same vendor as the line above | same change as the line above | Time to revision 119 days |
| 2026-06-03 | CVE-2026-0661 | same vendor as the line above | same change as the line above | Time to revision 119 days |
| 2026-06-03 | whole record autodesk | stated at publication 5.3, now states 5.5CVSS v3.1 · base scoreMediumMedium | Time to revision 8 days | |
| 2026-06-03 | CVE-2026-7450 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-06-03 | CVE-2026-7453 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-06-03 | CVE-2026-4480 | whole record redhat | stated at publication 8.5, now states 9.0CVSS v3.1 · base scoreHighCritical | Time to revision 8 days |
| Tue 2 Jun 2026· 1 change | ||||
| 2026-06-02 | CVE-2025-53345 | whole record Patchstack | stated at publication 6.5, now states 8.8CVSS v3.1 · base scoreMediumHigh | Time to revision 0 days |
| Fri 29 May 2026· 2 changes | ||||
| 2026-05-29 | CVE-2026-0257 | whole record palo_alto | stated at publication 4.7, now states 7.8CVSS v4.0 · base scoreMediumHigh | Time to revision 16 days |
| 2026-05-29 | CVE-2026-9828 | whole record NCSC.ch | stated at publication 1.2, now states 2.9CVSS v4.0 · base scoreLowLow | Time to revision 1 days |
| Wed 27 May 2026· 2 changes | ||||
| 2026-05-27 | CVE-2026-48999 | whole record zte | stated at publication 5.3, now states 5.7CVSS v3.1 · base scoreMediumMedium | Time to revision 0 days |
| 2026-05-27 | CVE-2026-49000 | whole record zte | stated at publication 5.3, now states 7.0CVSS v3.1 · base scoreMediumHigh | Time to revision 0 days |
| Tue 26 May 2026· 3 changes | ||||
| 2026-05-26 | CVE-2026-41947 | whole record VulnCheck | stated at publication 9.1, now states 9.3CVSS v4.0 · base scoreCriticalCritical | Time to revision 8 days |
| 2026-05-26 | CVE-2026-48132 | whole record checkpoint | stated at publication 7.4, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| 2026-05-26 | CVE-2026-48134 | whole record checkpoint | stated at publication 7.6, now states 5.6CVSS v3.1 · base scoreHighMedium | Time to revision 0 days |
| Thu 14 May 2026· 1 change | ||||
| 2026-05-14 | CVE-2026-20188 | whole record cisco | stated at publication 7.5, now states 0.0CVSS v3.1 · base scoreHighNone | Time to revision 8 days |
| Wed 13 May 2026· 4 changes | ||||
| 2026-05-13 | whole record adobe | stated at publication 5.5, now states 7.8CVSS v3.1 · base scoreMediumHigh | Time to revision 1 days | |
| 2026-05-13 | CVE-2026-34683 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-05-13 | CVE-2026-34684 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2026-05-13 | CVE-2026-44113 | whole record VulnCheck | stated at publication 6.0, now states 8.3CVSS v4.0 · base scoreMediumHigh | Time to revision 7 days |
| 2026-05-13 | CVE-2025-15101 | whole record ASUS | stated at publication 8.5, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 48 days |
| Tue 12 May 2026· 8 changes | ||||
| 2026-05-12 | CVE-2026-29204 | whole record hackerone | stated at publication 10.0, now states 9.1CVSS v3.1 · base scoreCriticalCritical | Time to revision 0 days |
| 2026-05-12 | CVE-2023-53878 | whole record VulnCheck | stated at publication 7.3, now states 6.9CVSS v4.0 · base scoreHighMedium | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53879 | whole record VulnCheck | stated at publication 5.3, now states 6.7CVSS v4.0 · base scoreMediumMedium | Time to revision 148 days |
| 2026-05-12 | whole record VulnCheck | stated at publication 7.2, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 148 days | |
| 2026-05-12 | CVE-2023-53883 | same vendor as the line above | same change as the line above | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53885 | same vendor as the line above | same change as the line above | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53888 | same vendor as the line above | same change as the line above | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53889 | same vendor as the line above | same change as the line above | Time to revision 148 days |
| 2026-05-12 | CVE-2023-53886 | whole record VulnCheck | stated at publication 5.7, now states 5.1CVSS v4.0 · base scoreMediumMedium | Time to revision 148 days |
| Sun 10 May 2026· 1 change | ||||
| 2026-05-10 | CVE-2026-5791 | whole record TR-CERT | stated at publication 9.6, now states 6.5CVSS v3.1 · base scoreCriticalMedium | Time to revision 3 days |
| Thu 30 Apr 2026· 1 change | ||||
| 2026-04-30 | CVE-2026-25990 | whole record GitHub_M | stated at publication 8.9, now states 8.6CVSS v4.0 · base scoreHighHigh | Time to revision 78 days |
| Wed 29 Apr 2026· 3 changes | ||||
| 2026-04-29 | CVE-2026-22740 | whole record vmware | stated at publication 0.0, now states 6.5CVSS v3.1 · base scoreNoneMedium | Time to revision 0 days |
| 2026-04-29 | CVE-2026-22741 | whole record vmware | stated at publication 0.0, now states 3.1CVSS v3.1 · base scoreNoneLow | Time to revision 0 days |
| 2026-04-29 | CVE-2026-5140 | whole record TR-CERT | stated at publication 9.6, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 0 days |
| Tue 28 Apr 2026· 29 changes | ||||
| 2026-04-28 | CVE-2023-25043 | whole record Patchstack | stated at publication 5.0, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 741 days |
| 2026-04-28 | whole record Patchstack | stated at publication 7.1, now states 5.8CVSS v3.1 · base scoreHighMedium | Time to revision 740 to 972 days | |
| 2026-04-28 | CVE-2023-25466 | same vendor as the line above | same change as the line above | Time to revision 972 days |
| 2026-04-28 | CVE-2024-32587 | same vendor as the line above | same change as the line above | Time to revision 740 days |
| 2026-04-28 | CVE-2023-28418 | whole record Patchstack | stated at publication 5.4, now states 7.1CVSS v3.1 · base scoreMediumHigh | Time to revision 1,041 days |
| 2026-04-28 | CVE-2023-32123 | whole record Patchstack | stated at publication 7.1, now states 6.1CVSS v3.1 · base scoreHighMedium | Time to revision 897 days |
| 2026-04-28 | whole record Patchstack | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 678 to 763 days | |
| 2026-04-28 | CVE-2023-32237 | same vendor as the line above | same change as the line above | Time to revision 763 days |
| 2026-04-28 | CVE-2023-35050 | same vendor as the line above | same change as the line above | Time to revision 678 days |
| 2026-04-28 | CVE-2023-46197 | whole record Patchstack | stated at publication 8.8, now states 5.3CVSS v3.1 · base scoreHighMedium | Time to revision 711 days |
| 2026-04-28 | CVE-2023-47504 | whole record Patchstack | stated at publication 7.5, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 734 days |
| 2026-04-28 | CVE-2023-51405 | whole record Patchstack | stated at publication 5.3, now states 8.2CVSS v3.1 · base scoreMediumHigh | Time to revision 734 days |
| 2026-04-28 | CVE-2023-51539 | whole record Patchstack | stated at publication 4.3, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 844 days |
| 2026-04-28 | CVE-2024-27955 | whole record Patchstack | stated at publication 8.3, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 711 days |
| 2026-04-28 | whole record Patchstack | stated at publication 6.5, now states 5.5CVSS v3.1 · base scoreMediumMedium | Time to revision 726 to 770 days | |
| 2026-04-28 | CVE-2024-29141 | same vendor as the line above | same change as the line above | Time to revision 770 days |
| 2026-04-28 | CVE-2024-33948 | same vendor as the line above | same change as the line above | Time to revision 726 days |
| 2026-04-28 | CVE-2024-29906 | whole record Patchstack | stated at publication 6.5, now states 5.9CVSS v3.1 · base scoreMediumMedium | Time to revision 763 days |
| 2026-04-28 | CVE-2024-30427 | whole record Patchstack | stated at publication 7.1, now states 5.4CVSS v3.1 · base scoreHighMedium | Time to revision 760 days |
| 2026-04-28 | CVE-2024-31098 | whole record Patchstack | stated at publication 8.1, now states 7.1CVSS v3.1 · base scoreHighHigh | Time to revision 688 days |
| 2026-04-28 | whole record Patchstack | stated at publication 7.1, now states 5.9CVSS v3.1 · base scoreHighMedium | Time to revision 645 to 740 days | |
| 2026-04-28 | CVE-2024-32585 | same vendor as the line above | same change as the line above | Time to revision 740 days |
| 2026-04-28 | CVE-2024-37432 | same vendor as the line above | same change as the line above | Time to revision 645 days |
| 2026-04-28 | whole record Patchstack | stated at publication 5.9, now states 6.5CVSS v3.1 · base scoreMediumMedium | Time to revision 689 to 712 days | |
| 2026-04-28 | CVE-2024-32800 | same vendor as the line above | same change as the line above | Time to revision 712 days |
| 2026-04-28 | CVE-2024-34567 | same vendor as the line above | same change as the line above | Time to revision 712 days |
| 2026-04-28 | CVE-2024-35751 | same vendor as the line above | same change as the line above | Time to revision 689 days |
| 2026-04-28 | CVE-2024-38728 | whole record Patchstack | stated at publication 7.2, now states 7.1CVSS v3.1 · base scoreHighHigh | Time to revision 645 days |
| 2026-04-28 | CVE-2024-38739 | whole record Patchstack | stated at publication 6.5, now states 5.1CVSS v3.1 · base scoreMediumMedium | Time to revision 648 days |
| 2026-04-28 | CVE-2025-24735 | whole record Patchstack | stated at publication 5.9, now states 7.7CVSS v3.1 · base scoreMediumHigh | Time to revision 298 days |
| 2026-04-28 | CVE-2026-40967 | whole record vmware | stated at publication 8.2, now states 8.6CVSS v3.1 · base scoreHighHigh | Time to revision 0 days |
| 2026-04-28 | CVE-2026-32589 | whole record redhat | stated at publication 7.1, now states 7.4CVSS v3.1 · base scoreHighHigh | Time to revision 20 days |
| 2026-04-28 | CVE-2025-54196 | whole record adobe | stated at publication 3.1, now states 4.3CVSS v3.1 · base scoreLowMedium | Time to revision 195 days |
| 2026-04-28 | CVE-2025-49552 | whole record adobe | stated at publication 7.3, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 195 days |
| Thu 23 Apr 2026· 25 changes | ||||
| 2026-04-23 | CVE-2024-37555 | whole record Patchstack | stated at publication 9.1, now states 9.6CVSS v3.1 · base scoreCriticalCriticalOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 631 days |
| 2026-04-23 | CVE-2024-43933 | whole record Patchstack | stated at publication 4.3, now states 7.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 517 days |
| 2026-04-23 | whole record Patchstack | stated at publication 6.5, now states 7.1CVSS v3.1 · base scoreMediumHighBranches and original-value intervals are stated on each row. | Time to revision 224 to 561 days | |
| 2026-04-23 | CVE-2024-43938 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 561 days |
| 2026-04-23 | CVE-2025-49411 | same vendor as the line above | same change as the line above | Time to revision 246 days |
| 2026-04-23 | CVE-2025-49420 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days |
| 2026-04-23 | CVE-2025-49424 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days |
| 2026-04-23 | CVE-2025-49893 | same vendor as the line above | same change as the line aboveOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days |
| 2026-04-23 | CVE-2024-47338 | whole record Patchstack | stated at publication 7.6, now states 8.5CVSS v3.1 · base scoreHighHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 542 days |
| 2026-04-23 | CVE-2024-47634 | whole record Patchstack | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 528 days |
| 2026-04-23 | CVE-2024-49256 | whole record Patchstack | stated at publication 5.4, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 516 days |
| 2026-04-23 | CVE-2024-50430 | whole record Patchstack | stated at publication 5.9, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 498 days |
| 2026-04-23 | CVE-2024-50441 | whole record Patchstack | stated at publication 7.4, now states 6.5CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 520 days |
| 2026-04-23 | CVE-2024-51676 | whole record Patchstack | stated at publication 7.1, now states 6.5CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 508 days |
| 2026-04-23 | CVE-2025-22704 | whole record Patchstack | stated at publication 5.4, now states 7.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 422 days |
| 2026-04-23 | CVE-2025-24748 | whole record Patchstack | stated at publication 8.5, now states 5.3CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 271 days |
| 2026-04-23 | CVE-2025-24757 | whole record Patchstack | stated at publication 6.5, now states 5.3CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 271 days |
| 2026-04-23 | CVE-2025-25081 | whole record Patchstack | stated at publication 4.2, now states 4.8CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 418 days |
| 2026-04-23 | CVE-2025-25121 | whole record Patchstack | stated at publication 7.1, now states 5.4CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 394 days |
| 2026-04-23 | CVE-2025-25162 | whole record Patchstack | stated at publication 7.5, now states 7.1CVSS v3.1 · base scoreHighHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 394 days |
| 2026-04-23 | CVE-2025-32180 | whole record Patchstack | stated at publication 4.3, now states 6.5CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 320 days |
| 2026-04-23 | CVE-2025-32245 | whole record Patchstack | stated at publication 8.5, now states 7.1CVSS v3.1 · base scoreHighHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 320 days |
| 2026-04-23 | CVE-2025-32281 | whole record Patchstack | stated at publication 9.8, now states 4.3CVSS v3.1 · base scoreCriticalMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 278 days |
| 2026-04-23 | CVE-2025-32642 | whole record Patchstack | stated at publication 10.0, now states 9.6CVSS v3.1 · base scoreCriticalCriticalOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 357 days |
| 2026-04-23 | CVE-2025-39537 | whole record Patchstack | stated at publication 5.3, now states 7.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 320 days |
| 2026-04-23 | CVE-2025-47444 | whole record Patchstack | stated at publication 7.5, now states 5.3CVSS v3.1 · base scoreHighMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 232 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 →