Every change, newest first
Showing changes seen on 2026-04-08. Every day
| 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. | Kind | Record or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together. | Vendor or package, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | What changed | Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong. |
|---|---|---|---|---|---|
| Wed 8 Apr 2026· 86 changes | |||||
| 2026-04-08 | CVSS base score changed | CVE-2023-3447 | whole record Wordfence | stated at publication 8.6, now states 7.6CVSS v3.1 · base scoreHighHigh | Time to revision 1,015 days |
| 2026-04-08 | CVSS base score changed | CVE-2023-5250 | whole record Wordfence | stated at publication 6.4, now states 8.8CVSS v3.1 · base scoreMediumHigh | Time to revision 891 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-0586 | whole record Wordfence | stated at publication 6.5, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 793 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-0956 | whole record Wordfence | stated at publication 7.2, now states 4.9CVSS v3.1 · base scoreHighMedium | Time to revision 741 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-10078 | whole record Wordfence | stated at publication 7.3, now states 6.3CVSS v3.1 · base scoreHighMedium | Time to revision 537 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-1125 | whole record Wordfence | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 761 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-1126 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 756 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-2392 | whole record Wordfence | stated at publication 6.5, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 748 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-2665 | whole record Wordfence | stated at publication 6.5, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 729 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-2792 | whole record Wordfence | stated at publication 6.5, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 729 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-3893 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 713 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-6521 | whole record Wordfence | stated at publication 5.5, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 620 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-6661 | whole record Wordfence | stated at publication 5.5, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 621 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-7857 | whole record Wordfence | stated at publication 9.8, now states 6.5CVSS v3.1 · base scoreCriticalMedium | Time to revision 588 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-8353 | whole record Wordfence | stated at publication 10.0, now states 9.8CVSS v3.1 · base scoreCriticalCritical | Time to revision 558 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14446 | whole record Wordfence | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 117 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-1319 | whole record Wordfence | stated at publication 6.4, now states 7.2CVSS v3.1 · base scoreMediumHigh | Time to revision 404 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-9849 | whole record Wordfence | stated at publication 5.3, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 215 days |
| 2026-04-08 | CVSS base score changed | CVE-2023-0555 | whole record Wordfence | stated at publication 7.6, now states 8.1CVSS v3.1 · base scoreHighHigh | Time to revision 1,167 days |
| 2026-04-08 | CVSS base score changed | CVE-2023-2079 | whole record Wordfence | stated at publication 8.3, now states 7.1CVSS v3.1 · base scoreHighHigh | Time to revision 1,003 days |
| 2026-04-08 | CVSS base score changed | CVE-2023-2436 | whole record Wordfence | stated at publication 5.5, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 1,044 days |
| 2026-04-08 | CVSS base score changed | CVE-2023-3244 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 965 days |
| 2026-04-08 | CVSS base score changed | CVE-2023-6933 | whole record Wordfence | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 793 days |
| 2026-04-08 | CVSS base score changed | CVE-2023-6969 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 756 days |
| 2026-04-08 | CVSS base score changed | CVE-2023-6979 | whole record Wordfence | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 818 days |
| 2026-04-08 | CVSS base score changed | CVE-2023-6994 | whole record Wordfence | stated at publication 6.5, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 818 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-0608 | whole record Wordfence | stated at publication 8.8, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 740 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-1689 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 671 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-2798 | whole record Wordfence | stated at publication 6.5, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 716 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-2948 | whole record Wordfence | stated at publication 7.2, now states 6.4CVSS v3.1 · base scoreHighMedium | Time to revision 739 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-3916 | whole record Wordfence | stated at publication 5.3, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 699 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-4262 | whole record Wordfence | stated at publication 7.2, now states 6.4CVSS v3.1 · base scoreHighMedium | Time to revision 686 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-4709 | whole record Wordfence | stated at publication 7.2, now states 6.4CVSS v3.1 · base scoreHighMedium | Time to revision 690 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-4743 | whole record Wordfence | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 672 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-6518 | whole record Wordfence | stated at publication 5.5, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 620 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-7856 | whole record Wordfence | stated at publication 9.1, now states 8.1CVSS v3.1 · base scoreCriticalHigh | Time to revision 588 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-9017 | whole record Wordfence | stated at publication 7.2, now states 6.4CVSS v3.1 · base scoreHighMedium | Time to revision 279 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-9860 | whole record Wordfence | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 544 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-11893 | whole record Wordfence | stated at publication 8.8, now states 6.5CVSS v3.1 · base scoreHighMedium | Time to revision 165 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-12451 | whole record Wordfence | stated at publication 6.1, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 49 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14151 | whole record Wordfence | stated at publication 6.1, now states 7.2CVSS v3.1 · base scoreMediumHigh | Time to revision 110 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14441 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 93 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14581 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 117 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14997 | whole record Wordfence | stated at publication 7.2, now states 8.8CVSS v3.1 · base scoreHighHigh | Time to revision 93 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-2636 | whole record Wordfence | stated at publication 9.8, now states 8.1CVSS v3.1 · base scoreCriticalHigh | Time to revision 363 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-0745 | whole record Wordfence | stated at publication 7.2, now states 5.5CVSS v3.1 · base scoreHighMedium | Time to revision 54 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-1253 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 19 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-1389 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 70 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-1937 | whole record Wordfence | stated at publication 9.8, now states 7.2CVSS v3.1 · base scoreCriticalHigh | Time to revision 50 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-2290 | whole record Wordfence | stated at publication 6.5, now states 3.8CVSS v3.1 · base scoreMediumLow | Time to revision 19 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-2991 | whole record Wordfence | stated at publication 9.8, now states 7.3CVSS v3.1 · base scoreCriticalHigh | Time to revision 21 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-4127 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 19 days |
| 2026-04-08 | CVSS base score changed | CVE-2023-6972 | whole record Wordfence | stated at publication 7.5, now states 9.8CVSS v3.1 · base scoreHighCritical | Time to revision 838 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-12472 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 453 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-12599 | whole record Wordfence | stated at publication 7.2, now states 6.4CVSS v3.1 · base scoreHighMedium | Time to revision 422 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-13449 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 438 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-1686 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 772 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-1771 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 764 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-4448 | whole record Wordfence | stated at publication 6.5, now states 6.4CVSS v3.1 · base scoreMediumMedium | Time to revision 698 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-4742 | whole record Wordfence | stated at publication 9.8, now states 6.5CVSS v3.1 · base scoreCriticalMedium | Time to revision 658 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-4838 | whole record Wordfence | stated at publication 8.8, now states 7.5CVSS v3.1 · base scoreHighHigh | Time to revision 692 days |
| 2026-04-08 | CVSS base score changed | CVE-2024-6520 | whole record Wordfence | stated at publication 5.5, now states 4.4CVSS v3.1 · base scoreMediumMedium | Time to revision 620 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-10054 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 138 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-10744 | whole record Wordfence | stated at publication 5.3, now states 5.9CVSS v3.1 · base scoreMediumMedium | Time to revision 190 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-12560 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 154 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-13403 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 117 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14064 | whole record Wordfence | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 118 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14065 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 117 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14074 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 117 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14170 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 118 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14370 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 91 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-14447 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 117 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-3953 | whole record Wordfence | stated at publication 6.5, now states 5.4CVSS v3.1 · base scoreMediumMedium | Time to revision 344 days |
| 2026-04-08 | CVSS base score changed | CVE-2025-5701 | whole record Wordfence | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 307 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-0820 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 82 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-1298 | whole record Wordfence | stated at publication 5.3, now states 4.3CVSS v3.1 · base scoreMediumMedium | Time to revision 71 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-1499 | whole record Wordfence | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 61 days |
| 2026-04-08 | CVSS base score changed | CVE-2026-4484 | whole record Wordfence | stated at publication 9.8, now states 8.8CVSS v3.1 · base scoreCriticalHigh | Time to revision 14 days |
| 2026-04-08 | Record state changed | CVE-2026-34402 | whole record GitHub_M | stated at publication PUBLISHED, now states REJECTED | Time to revision 2 days |
| 2026-04-08 | Record state changed | CVE-2026-35567 | whole record GitHub_M | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| 2026-04-08 | Record state changed | CVE-2026-39317 | whole record GitHub_M | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| 2026-04-08 | Record state changed | CVE-2026-39323 | whole record GitHub_M | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| 2026-04-08 | Record state changed | CVE-2026-33817 | whole record Go | stated at publication PUBLISHED, now states REJECTED | Time to revision 2 days |
| 2026-04-08published 2026-04-03 | Advisory fix version moved | GHSA-rp9m-7r4c-75qgCVE-2026-35039 | npmfast-jwt critical | stated at publication 6.1.0, now states 6.2.0 | Time to revision 5 days |
| 2026-04-08published 2026-03-20 | Package added to advisory | GHSA-687q-32c6-8x68CVE-2026-33478 | critical | not named as affected when the advisory was published, now names wwbn/avideo | Time to revision 19 days |
| 2026-04-08published 2026-03-03 | Advisory severity changed | GHSA-8fmp-37rc-p5g7CVE-2026-22177 | whole advisorymoderate | stated at publication HIGH, now states MODERATEA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | Time to revision 36 days |
Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.
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 →