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. |
|---|---|---|---|---|
| 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 |
| Tue 28 Apr 2026· 25 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 |
| Thu 23 Apr 2026· 52 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 |
| 2026-04-23 | CVE-2025-49288 | whole record Patchstack | stated at publication 4.3, now states 8.8CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 299 days |
| 2026-04-23 | whole record Patchstack | stated at publication 6.5, now states 9.8CVSS v3.1 · base scoreMediumCriticalBranches and original-value intervals are stated on each row. | Time to revision 224 to 246 days | |
| 2026-04-23 | CVE-2025-49400 | same vendor as the line above | same change as the line above | Time to revision 246 days |
| 2026-04-23 | CVE-2025-49422 | 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-49402 | whole record Patchstack | stated at publication 6.5, now states 8.5CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 216 days |
| 2026-04-23 | CVE-2025-49405 | whole record Patchstack | stated at publication 8.1, now states 4.3CVSS v3.1 · base scoreHighMedium | Time to revision 238 days |
| 2026-04-23 | CVE-2025-49406 | whole record Patchstack | stated at publication 5.3, now states 8.5CVSS v3.1 · base scoreMediumHigh | Time to revision 246 days |
| 2026-04-23 | CVE-2025-49407 | whole record Patchstack | stated at publication 7.1, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 238 days |
| 2026-04-23 | CVE-2025-49408 | whole record Patchstack | stated at publication 4.9, now states 10.0CVSS v3.1 · base scoreMediumCritical | Time to revision 246 days |
| 2026-04-23 | whole record Patchstack | stated at publication 5.9, now states 9.8CVSS v3.1 · base scoreMediumCriticalBranches and original-value intervals are stated on each row. | Time to revision 224 to 246 days | |
| 2026-04-23 | CVE-2025-49409 | same vendor as the line above | same change as the line above | Time to revision 246 days |
| 2026-04-23 | CVE-2025-49434 | 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-49890 | 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-49410 | whole record Patchstack | stated at publication 6.5, now states 10.0CVSS v3.1 · base scoreMediumCritical | Time to revision 246 days |
| 2026-04-23 | CVE-2025-49413 | whole record Patchstack | stated at publication 5.9, now states 7.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days |
| 2026-04-23 | CVE-2025-49426 | whole record Patchstack | stated at publication 4.3, now states 8.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days |
| 2026-04-23 | CVE-2025-49428 | whole record Patchstack | stated at publication 5.9, now states 7.5CVSS v3.1 · base scoreMediumHigh | Time to revision 246 days |
| 2026-04-23 | CVE-2025-49436 | whole record Patchstack | stated at publication 6.5, now states 8.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days |
| 2026-04-23 | CVE-2025-49438 | whole record Patchstack | stated at publication 7.2, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 246 days |
| 2026-04-23 | CVE-2025-49455 | whole record Patchstack | stated at publication 9.8, now states 9.3CVSS v3.1 · base scoreCriticalCriticalOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 295 days |
| 2026-04-23 | whole record Patchstack | stated at publication 5.9, now states 8.1CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days | |
| 2026-04-23 | CVE-2025-49889 | 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-49892 | 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-49894 | 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-49891 | whole record Patchstack | stated at publication 5.9, now states 8.5CVSS v3.1 · base scoreMediumHighOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 224 days |
| 2026-04-23 | CVE-2025-49895 | whole record Patchstack | stated at publication 8.8, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 251 days |
| 2026-04-23 | CVE-2025-49896 | whole record Patchstack | stated at publication 4.3, now states 5.3CVSS v3.1 · base scoreMediumMedium | Time to revision 246 days |
| 2026-04-23 | CVE-2025-49897 | whole record Patchstack | stated at publication 8.5, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 251 days |
| 2026-04-23 | CVE-2025-49898 | whole record Patchstack | stated at publication 5.9, now states 7.6CVSS v3.1 · base scoreMediumHigh | Time to revision 251 days |
| 2026-04-23 | CVE-2025-62138 | whole record Patchstack | stated at publication 5.3, now states 5.4CVSS v3.1 · base scoreMediumMediumOriginal value first replaced 2026-04-01; this value first seen 2026-04-23. | Time to revision 91 days |
| Mon 15 Sep 2025· 1 change | ||||
| 2025-09-15 | CVE-2025-58795 | whole record Patchstack | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 10 days |
| Mon 19 May 2025· 1 change | ||||
| 2025-05-19 | CVE-2025-24661 | whole record Patchstack | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 105 days |
| Mon 13 May 2024· 1 change | ||||
| 2024-05-13 | CVE-2024-34555 | whole record Patchstack | stated at publication 10.0, now states 9.1CVSS v3.1 · base scoreCriticalCritical | Time to revision 0 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 →