Every change, newest first
| 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, Which record was edited, by its CVE id, or how many records one collapsed line stands on. | Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | What changed | Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong. |
|---|---|---|---|---|---|
| Wed 19 Aug 2026· 2 changes | |||||
| 2026-08-192 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 4 to 31 days | |
| 2026-08-19 | same kind of change as the line above | CVE-2026-74511 | same vendor as the line above | same change as the line above | Time to revision 4 days |
| 2026-08-19 | same kind of change as the line above | CVE-2026-64158 | same vendor as the line above | same change as the line above | Time to revision 31 days |
| Mon 17 Aug 2026· 3 changes | |||||
| 2026-08-17 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 2 to 7 days | |
| 2026-08-17 | same kind of change as the line above | CVE-2026-68101 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| 2026-08-17 | same kind of change as the line above | CVE-2026-72044 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2026-08-17 | same kind of change as the line above | CVE-2026-72246 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| Tue 11 Aug 2026· 4 changes | |||||
| 2026-08-11 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 to 130 days | |
| 2026-08-11 | same kind of change as the line above | CVE-2026-31404 | same vendor as the line above | same change as the line above | Time to revision 130 days |
| 2026-08-11 | same kind of change as the line above | CVE-2026-46194 | same vendor as the line above | same change as the line above | Time to revision 75 days |
| 2026-08-11 | same kind of change as the line above | CVE-2026-63872 | same vendor as the line above | same change as the line above | Time to revision 23 days |
| 2026-08-11 | same kind of change as the line above | CVE-2026-68171 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| Fri 7 Aug 2026· 4 changes | |||||
| 2026-08-07 | Fix version moved | CVE-2026-68480 | linuxlinux | stated at publication 5.10.263, now states 5.10.264Release branch starts at 5.10.*.same day | Time to revision 1 days |
| 2026-08-07 | Fix version moved | CVE-2026-68480 | linuxlinux | stated at publication 5.15.214, now states 5.15.215Release branch starts at 5.15.*.same day | Time to revision 1 days |
| 2026-08-07 | Fix version moved | CVE-2026-68480 | linuxlinux | stated at publication 6.1.181, now states 6.1.182Release branch starts at 6.1.*.same day | Time to revision 1 days |
| 2026-08-07 | Fix version moved | CVE-2026-68480 | linuxlinux | stated at publication 6.6.149, now states 6.6.150Release branch starts at 6.6.*.same day | Time to revision 1 days |
| Fri 10 Jul 2026· 1 change | |||||
| 2026-07-10 | Record state changed | CVE-2026-53166 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 15 days |
| Fri 19 Jun 2026· 4 changes | |||||
| 2026-06-19 | Fix version moved | CVE-2026-43064 | linuxlinux | stated at publication 6.1.168, now states 6.1.176Release branch starts at 6.1.*.Original value first replaced 2026-06-01; this value first seen 2026-06-19. | Time to revision 27 days |
| 2026-06-19 | Fix version moved | CVE-2026-45852 | linuxlinux | stated at publication 5.10.252, now states 5.10.259Release branch starts at 5.10.*. | Time to revision 23 days |
| 2026-06-19 | Fix version moved | CVE-2026-45852 | linuxlinux | stated at publication 5.15.202, now states 5.15.210Release branch starts at 5.15.*. | Time to revision 23 days |
| 2026-06-19 | Fix version moved | CVE-2026-45852 | linuxlinux | stated at publication 6.1.165, now states 6.1.176Release branch starts at 6.1.*. | Time to revision 23 days |
| Wed 17 Jun 2026· 5 changes | |||||
| 2026-06-172 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 40 to 303 days | |
| 2026-06-17 | same kind of change as the line above | CVE-2026-43122 | same vendor as the line above | same change as the line above | Time to revision 42 days |
| 2026-06-17 | same kind of change as the line above | CVE-2025-38553 | same vendor as the line above | same change as the line above | Time to revision 303 days |
| 2026-06-17 | same kind of change as the line above | CVE-2026-31688 | same vendor as the line above | same change as the line above | Time to revision 51 days |
| 2026-06-17 | same kind of change as the line above | CVE-2026-43422 | same vendor as the line above | same change as the line above | Time to revision 40 days |
| 2026-06-17 | same kind of change as the line above | CVE-2026-43423 | same vendor as the line above | same change as the line above | Time to revision 40 days |
| Mon 15 Jun 2026· 3 changes | |||||
| 2026-06-15 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 18 to 19 days | |
| 2026-06-15 | same kind of change as the line above | CVE-2026-45992 | same vendor as the line above | same change as the line above | Time to revision 19 days |
| 2026-06-15 | same kind of change as the line above | CVE-2026-46217 | same vendor as the line above | same change as the line above | Time to revision 18 days |
| 2026-06-15 | same kind of change as the line above | CVE-2026-46237 | same vendor as the line above | same change as the line above | Time to revision 18 days |
| Mon 4 May 2026· 1 change | |||||
| 2026-05-04 | Fix version moved | CVE-2026-23112 | linuxlinux | stated at publication 5.10.250, now states 5.10.253Release branch starts at 5.10.*. | Time to revision 80 days |
| Sat 2 May 2026· 2 changes | |||||
| 2026-05-02 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 29 to 99 days | |
| 2026-05-02 | same kind of change as the line above | CVE-2025-71149 | same vendor as the line above | same change as the line above | Time to revision 99 days |
| 2026-05-02 | same kind of change as the line above | CVE-2026-23473 | same vendor as the line above | same change as the line above | Time to revision 29 days |
| Sat 25 Apr 2026· 1 change | |||||
| 2026-04-25 | Record state changed | CVE-2026-31534 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| Mon 13 Apr 2026· 2 changes | |||||
| 2026-04-13 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 10 to 19 days | |
| 2026-04-13 | same kind of change as the line above | CVE-2026-23333 | same vendor as the line above | same change as the line above | Time to revision 19 days |
| 2026-04-13 | same kind of change as the line above | CVE-2026-23471 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| Fri 3 Apr 2026· 8 changes | |||||
| 2026-04-03 | Fix version moved | CVE-2025-40219 | linuxlinux | stated at publication 5.10.246, now states 5.10.252Release branch starts at 5.10.*. | Time to revision 120 days |
| 2026-04-03 | Fix version moved | CVE-2025-40219 | linuxlinux | stated at publication 5.15.195, now states 5.15.202Release branch starts at 5.15.*. | Time to revision 120 days |
| 2026-04-03 | Fix version moved | CVE-2025-40219 | linuxlinux | stated at publication 6.1.157, now states 6.1.165Release branch starts at 6.1.*. | Time to revision 120 days |
| 2026-04-03 | Fix version moved | CVE-2025-40219 | linuxlinux | stated at publication 6.12.54, now states 6.12.75Release branch starts at 6.12.*. | Time to revision 120 days |
| 2026-04-03 | Fix version moved | CVE-2025-40219 | linuxlinux | stated at publication 6.6.113, now states 6.6.128Release branch starts at 6.6.*. | Time to revision 120 days |
| 2026-04-03 | Fix version moved | CVE-2025-40219 | linuxlinux | stated at publication 6.18, now states 6.18.16Release branch starts at *. | Duration unknown |
| 2026-04-032 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 9 to 80 days | |
| 2026-04-03 | same kind of change as the line above | CVE-2026-23320 | same vendor as the line above | same change as the line above | Time to revision 9 days |
| 2026-04-03 | same kind of change as the line above | CVE-2025-68812 | same vendor as the line above | same change as the line above | Time to revision 80 days |
| Mon 23 Mar 2026· 1 change | |||||
| 2026-03-23 | Record state changed | CVE-2024-27042 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 691 days |
| Thu 26 Feb 2026· 2 changes | |||||
| 2026-02-26 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 8 days | |
| 2026-02-26 | same kind of change as the line above | CVE-2025-71226 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2026-02-26 | same kind of change as the line above | CVE-2025-71228 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| Tue 10 Feb 2026· 1 change | |||||
| 2026-02-10 | Record state changed | CVE-2025-68789 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 28 days |
| Sat 31 Jan 2026· 1 change | |||||
| 2026-01-31 | Record state changed | CVE-2024-42130 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 550 days |
| Fri 9 Jan 2026· 1 change | |||||
| 2026-01-09 | Record state changed | CVE-2025-40361 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 24 days |
| Mon 5 Jan 2026· 7 changes | |||||
| 2026-01-053 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 12 to 585 days | |
| 2026-01-05 | same kind of change as the line above | CVE-2024-44972 | same vendor as the line above | same change as the line above | Time to revision 488 days |
| 2026-01-05 | same kind of change as the line above | CVE-2024-47672 | same vendor as the line above | same change as the line above | Time to revision 453 days |
| 2026-01-05 | same kind of change as the line above | CVE-2024-56781 | same vendor as the line above | same change as the line above | Time to revision 362 days |
| 2026-01-05 | same kind of change as the line above | CVE-2023-53183 | same vendor as the line above | same change as the line above | Time to revision 112 days |
| 2026-01-05 | same kind of change as the line above | CVE-2023-54029 | same vendor as the line above | same change as the line above | Time to revision 12 days |
| 2026-01-05 | same kind of change as the line above | CVE-2024-36923 | same vendor as the line above | same change as the line above | Time to revision 585 days |
| 2026-01-05 | same kind of change as the line above | CVE-2023-53779 | same vendor as the line above | same change as the line above | Time to revision 27 days |
| Fri 2 Jan 2026· 4 changes | |||||
| 2026-01-02 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 17 to 227 days | |
| 2026-01-02 | same kind of change as the line above | CVE-2025-37942 | same vendor as the line above | same change as the line above | Time to revision 227 days |
| 2026-01-02 | same kind of change as the line above | CVE-2025-38073 | same vendor as the line above | same change as the line above | Time to revision 198 days |
| 2026-01-02 | same kind of change as the line above | CVE-2025-68203 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| 2026-01-02 | same kind of change as the line above | CVE-2025-68224 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| Tue 30 Dec 2025· 5 changes | |||||
| 2025-12-302 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 0 to 6 days | |
| 2025-12-30 | same kind of change as the line above | CVE-2023-54054 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2025-12-30 | same kind of change as the line above | CVE-2023-54103 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2025-12-30 | same kind of change as the line above | CVE-2023-54256 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-12-30 | same kind of change as the line above | CVE-2023-54290 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-12-30 | same kind of change as the line above | CVE-2023-54212 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| Mon 29 Dec 2025· 6 changes | |||||
| 2025-12-293 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 5 to 490 days | |
| 2025-12-29 | same kind of change as the line above | CVE-2023-53469 | same vendor as the line above | same change as the line above | Time to revision 89 days |
| 2025-12-29 | same kind of change as the line above | CVE-2023-54082 | same vendor as the line above | same change as the line above | Time to revision 5 days |
| 2025-12-29 | same kind of change as the line above | CVE-2023-54161 | same vendor as the line above | same change as the line above | Time to revision 5 days |
| 2025-12-29 | same kind of change as the line above | CVE-2024-43895 | same vendor as the line above | same change as the line above | Time to revision 490 days |
| 2025-12-29 | same kind of change as the line above | CVE-2023-53749 | same vendor as the line above | same change as the line above | Time to revision 22 days |
| 2025-12-29 | same kind of change as the line above | CVE-2023-54061 | same vendor as the line above | same change as the line above | Time to revision 5 days |
| Tue 9 Dec 2025· 2 changes | |||||
| 2025-12-09 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days | |
| 2025-12-09 | same kind of change as the line above | CVE-2023-53805 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-12-09 | same kind of change as the line above | CVE-2023-53835 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| Fri 21 Nov 2025· 1 change | |||||
| 2025-11-21 | Record state changed | CVE-2025-40144 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 9 days |
| Thu 13 Nov 2025· 1 change | |||||
| 2025-11-13 | Record state changed | CVE-2025-40128 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| Wed 29 Oct 2025· 1 change | |||||
| 2025-10-29 | Record state changed | CVE-2023-53293 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 43 days |
| Fri 24 Oct 2025· 1 change | |||||
| 2025-10-24 | Record state changed | CVE-2025-39898 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 23 days |
| Thu 23 Oct 2025· 1 change | |||||
| 2025-10-23 | Record state changed | CVE-2023-53701 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| Tue 7 Oct 2025· 1 change | |||||
| 2025-10-07 | Record state changed | CVE-2023-52979 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 194 days |
| Mon 6 Oct 2025· 1 change | |||||
| 2025-10-06 | Record state changed | CVE-2025-39751 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 25 days |
| Thu 2 Oct 2025· 7 changes | |||||
| 2025-10-02 | Fix version moved | CVE-2025-38709 | linuxlinux | stated at publication 6.6.103, now states 6.6.109Release branch starts at 6.6.*.Original value first replaced 2025-09-25; this value first seen 2025-10-02. | Time to revision 21 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 4.19.276, now states 4.19.281Release branch starts at 4.19.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 5.10.173, now states 5.10.178Release branch starts at 5.10.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 5.15.99, now states 5.15.108Release branch starts at 5.15.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 5.4.235, now states 5.4.241Release branch starts at 5.4.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 6.1.16, now states 6.1.25Release branch starts at 6.1.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| 2025-10-02 | Fix version moved | CVE-2023-53431 | linuxlinux | stated at publication 6.2.3, now states 6.2.12Release branch starts at 6.2.*.Original value first replaced 2025-10-01; this value first seen 2025-10-02. | Time to revision 13 days |
| Wed 1 Oct 2025· 1 change | |||||
| 2025-10-01 | Record state changed | CVE-2023-53502 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days |
| Mon 29 Sep 2025· 2 changes | |||||
| 2025-09-29 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 6 to 17 days | |
| 2025-09-29 | same kind of change as the line above | CVE-2025-39799 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| 2025-09-29 | same kind of change as the line above | CVE-2025-39867 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| Wed 17 Sep 2025· 1 change | |||||
| 2025-09-17 | Record state changed | CVE-2025-38380 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 54 days |
| Tue 16 Sep 2025· 2 changes | |||||
| 2025-09-162 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 0 to 1 days | |
| 2025-09-16 | same kind of change as the line above | CVE-2023-53227 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2025-09-16 | same kind of change as the line above | CVE-2023-53283 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| Mon 15 Sep 2025· 1 change | |||||
| 2025-09-15 | Record state changed | CVE-2023-53212 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days |
| Fri 5 Sep 2025· 3 changes | |||||
| 2025-09-053 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 17 to 126 days | |
| 2025-09-05 | same kind of change as the line above | CVE-2023-53137 | same vendor as the line above | same change as the line above | Time to revision 126 days |
| 2025-09-05 | same kind of change as the line above | CVE-2025-38611 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| 2025-09-05 | same kind of change as the line above | CVE-2025-38603 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| Mon 11 Aug 2025· 1 change | |||||
| 2025-08-11 | Record state changed | CVE-2025-38213 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 38 days |
| Mon 28 Jul 2025· 1 change | |||||
| 2025-07-28 | Record state changed | CVE-2025-38178 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 24 days |
| Tue 15 Jul 2025· 1 change | |||||
| 2025-07-15 | Record state changed | CVE-2023-53001 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 110 days |
| Thu 19 Jun 2025· 9 changes | |||||
| 2025-06-193 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 1 to 441 days | |
| 2025-06-19 | same kind of change as the line above | CVE-2024-36022 | same vendor as the line above | same change as the line above | Time to revision 385 days |
| 2025-06-19 | same kind of change as the line above | CVE-2024-44955 | same vendor as the line above | same change as the line above | Time to revision 288 days |
| 2025-06-19 | same kind of change as the line above | CVE-2023-52733 | same vendor as the line above | same change as the line above | Time to revision 394 days |
| 2025-06-19 | same kind of change as the line above | CVE-2024-26794 | same vendor as the line above | same change as the line above | Time to revision 441 days |
| 2025-06-19 | same kind of change as the line above | CVE-2024-35788 | same vendor as the line above | same change as the line above | Time to revision 398 days |
| 2025-06-19 | same kind of change as the line above | CVE-2024-46700 | same vendor as the line above | same change as the line above | Time to revision 279 days |
| 2025-06-19 | same kind of change as the line above | CVE-2024-56786 | same vendor as the line above | same change as the line above | Time to revision 162 days |
| 2025-06-19 | same kind of change as the line above | CVE-2024-57920 | same vendor as the line above | same change as the line above | Time to revision 151 days |
| 1 more row in this change is not listed here. Open all 9 rows → | |||||
| Wed 18 Jun 2025· 4 changes | |||||
| 2025-06-183 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 0 to 240 days | |
| 2025-06-18 | same kind of change as the line above | CVE-2024-50032 | same vendor as the line above | same change as the line above | Time to revision 240 days |
| 2025-06-18 | same kind of change as the line above | CVE-2025-37976 | same vendor as the line above | same change as the line above | Time to revision 29 days |
| 2025-06-18 | same kind of change as the line above | CVE-2025-38026 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-06-18 | same kind of change as the line above | CVE-2025-38046 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| Thu 5 Jun 2025· 1 change | |||||
| 2025-06-05 | Record state changed | CVE-2023-53025 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 70 days |
| Wed 4 Jun 2025· 2 changes | |||||
| 2025-06-042 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 27 to 34 days | |
| 2025-06-04 | same kind of change as the line above | CVE-2025-37782 | same vendor as the line above | same change as the line above | Time to revision 34 days |
| 2025-06-04 | same kind of change as the line above | CVE-2025-37832 | same vendor as the line above | same change as the line above | Time to revision 27 days |
| Mon 26 May 2025· 3 changes | |||||
| 2025-05-262 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 6 to 361 days | |
| 2025-05-26 | same kind of change as the line above | CVE-2024-36907 | same vendor as the line above | same change as the line above | Time to revision 361 days |
| 2025-05-26 | same kind of change as the line above | CVE-2025-37753 | same vendor as the line above | same change as the line above | Time to revision 25 days |
| 2025-05-26 | same kind of change as the line above | CVE-2025-37902 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| Tue 20 May 2025· 4 changes | |||||
| 2025-05-20 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 12 to 121 days | |
| 2025-05-20 | same kind of change as the line above | CVE-2025-21633 | same vendor as the line above | same change as the line above | Time to revision 121 days |
| 2025-05-20 | same kind of change as the line above | CVE-2025-21686 | same vendor as the line above | same change as the line above | Time to revision 99 days |
| 2025-05-20 | same kind of change as the line above | CVE-2025-21837 | same vendor as the line above | same change as the line above | Time to revision 74 days |
| 2025-05-20 | same kind of change as the line above | CVE-2025-37804 | same vendor as the line above | same change as the line above | Time to revision 12 days |
| Sat 10 May 2025· 5 changes | |||||
| 2025-05-103 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 1 to 302 days | |
| 2025-05-10 | same kind of change as the line above | CVE-2023-53063 | same vendor as the line above | same change as the line above | Time to revision 8 days |
| 2025-05-10 | same kind of change as the line above | CVE-2024-39501 | same vendor as the line above | same change as the line above | Time to revision 302 days |
| 2025-05-10 | same kind of change as the line above | CVE-2024-50016 | same vendor as the line above | same change as the line above | Time to revision 201 days |
| 2025-05-10 | same kind of change as the line above | CVE-2025-37795 | same vendor as the line above | same change as the line above | Time to revision 9 days |
| 2025-05-10 | same kind of change as the line above | CVE-2025-37835 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| Thu 8 May 2025· 5 changes | |||||
| 2025-05-08 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 6 to 7 days | |
| 2025-05-08 | same kind of change as the line above | CVE-2023-53104 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2025-05-08 | same kind of change as the line above | CVE-2023-53122 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2025-05-08 | same kind of change as the line above | CVE-2023-53129 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2025-05-08 | same kind of change as the line above | CVE-2023-53130 | same vendor as the line above | same change as the line above | Time to revision 6 days |
| 2025-05-08 | same kind of change as the line above | CVE-2025-23139 | same vendor as the line above | same change as the line above | Time to revision 7 days |
| Mon 5 May 2025· 1 change | |||||
| 2025-05-05 | Record state changed | CVE-2023-53076 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 3 days |
| Thu 1 May 2025· 1 change | |||||
| 2025-05-01 | Record state changed | CVE-2025-22029 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 15 days |
| Fri 25 Apr 2025· 3 changes | |||||
| 2025-04-25 | Fix version moved | CVE-2025-22077 | linuxlinux | stated at publication 6.12.23, now states 6.12.25Release branch starts at 6.12.*.Original value first replaced 2025-04-22; this value first seen 2025-04-25. | Time to revision 6 days |
| 2025-04-25 | Fix version moved | CVE-2025-22077 | linuxlinux | stated at publication 6.14.2, now states 6.14.4Release branch starts at 6.14.*.Original value first replaced 2025-04-22; this value first seen 2025-04-25. | Time to revision 6 days |
| 2025-04-25 | Fix version moved | CVE-2025-22077 | linuxlinux | stated at publication 6.6.87, now states 6.6.88Release branch starts at 6.6.*.Original value first replaced 2025-04-22; this value first seen 2025-04-25. | Time to revision 6 days |
| Thu 24 Apr 2025· 1 change | |||||
| 2025-04-24 | Record state changed | CVE-2024-49995 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 185 days |
| Wed 2 Apr 2025· 1 change | |||||
| 2025-04-02 | Record state changed | CVE-2024-54680 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 81 days |
| Tue 1 Apr 2025· 1 change | |||||
| 2025-04-01 | Record state changed | CVE-2023-52990 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 5 days |
| Fri 28 Mar 2025· 2 changes | |||||
| 2025-03-28 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 to 72 days | |
| 2025-03-28 | same kind of change as the line above | CVE-2023-53027 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| 2025-03-28 | same kind of change as the line above | CVE-2024-57894 | same vendor as the line above | same change as the line above | Time to revision 72 days |
| Thu 27 Mar 2025· 2 changes | |||||
| 2025-03-27 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 29 days | |
| 2025-03-27 | same kind of change as the line above | CVE-2025-21740 | same vendor as the line above | same change as the line above | Time to revision 29 days |
| 2025-03-27 | same kind of change as the line above | CVE-2025-21755 | same vendor as the line above | same change as the line above | Time to revision 29 days |
| Tue 25 Mar 2025· 1 change | |||||
| 2025-03-25 | Record state changed | CVE-2025-21757 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 26 days |
| Mon 10 Mar 2025· 1 change | |||||
| 2025-03-10 | Record state changed | CVE-2024-27055 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 313 days |
| Mon 3 Mar 2025· 3 changes | |||||
| 2025-03-03 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 64 to 133 days | |
| 2025-03-03 | same kind of change as the line above | CVE-2023-52917 | same vendor as the line above | same change as the line above | Time to revision 133 days |
| 2025-03-03 | same kind of change as the line above | CVE-2024-50181 | same vendor as the line above | same change as the line above | Time to revision 115 days |
| 2025-03-03 | same kind of change as the line above | CVE-2024-56741 | same vendor as the line above | same change as the line above | Time to revision 64 days |
| Sun 2 Mar 2025· 1 change | |||||
| 2025-03-02 | Record state changed | CVE-2025-21818 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 3 days |
| Thu 27 Feb 2025· 1 change | |||||
| 2025-02-27 | Record state changed | CVE-2024-36942 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 273 days |
| Mon 24 Feb 2025· 1 change | |||||
| 2025-02-24 | Record state changed | CVE-2024-40982 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 227 days |
| Thu 13 Feb 2025· 4 changes | |||||
| 2025-02-132 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 1 to 48 days | |
| 2025-02-13 | same kind of change as the line above | CVE-2024-53689 | same vendor as the line above | same change as the line above | Time to revision 33 days |
| 2025-02-13 | same kind of change as the line above | CVE-2024-57915 | same vendor as the line above | same change as the line above | Time to revision 25 days |
| 2025-02-13 | same kind of change as the line above | CVE-2024-56571 | same vendor as the line above | same change as the line above | Time to revision 48 days |
| 2025-02-13 | same kind of change as the line above | CVE-2025-21698 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| Wed 5 Feb 2025· 1 change | |||||
| 2025-02-05 | Record state changed | CVE-2024-41071 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 191 days |
| Fri 24 Jan 2025· 2 changes | |||||
| 2025-01-24 | Fix version moved | CVE-2024-26885 | linuxlinux | stated at publication 5.10.214, now states 5.10.227Release branch starts at 5.10.*. | Time to revision 282 days |
| 2025-01-24 | Fix version moved | CVE-2025-21654 | linuxlinux | stated at publication 6.6.72, now states 6.6.74Release branch starts at 6.6.*. | Time to revision 5 days |
| Wed 22 Jan 2025· 1 change | |||||
| 2025-01-22 | Record state changed | CVE-2024-57937 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 days |
| Fri 17 Jan 2025· 1 change | |||||
| 2025-01-17 | Record state changed | CVE-2025-21630 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 2 days |
| Sat 11 Jan 2025· 5 changes | |||||
| 2025-01-11 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 0 days | |
| 2025-01-11 | same kind of change as the line above | CVE-2025-23124 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-01-11 | same kind of change as the line above | CVE-2025-23125 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-01-11 | same kind of change as the line above | CVE-2025-23126 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-01-11 | same kind of change as the line above | CVE-2025-23127 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| 2025-01-11 | same kind of change as the line above | CVE-2025-23128 | same vendor as the line above | same change as the line above | Time to revision 0 days |
| Thu 9 Jan 2025· 4 changes | |||||
| 2025-01-09 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 16 to 113 days | |
| 2025-01-09 | same kind of change as the line above | CVE-2024-46756 | same vendor as the line above | same change as the line above | Time to revision 113 days |
| 2025-01-09 | same kind of change as the line above | CVE-2024-46757 | same vendor as the line above | same change as the line above | Time to revision 113 days |
| 2025-01-09 | same kind of change as the line above | CVE-2024-46758 | same vendor as the line above | same change as the line above | Time to revision 113 days |
| 2025-01-09 | same kind of change as the line above | CVE-2024-53159 | same vendor as the line above | same change as the line above | Time to revision 16 days |
| Tue 7 Jan 2025· 3 changes | |||||
| 2025-01-07 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 1 to 78 days | |
| 2025-01-07 | same kind of change as the line above | CVE-2024-49967 | same vendor as the line above | same change as the line above | Time to revision 78 days |
| 2025-01-07 | same kind of change as the line above | CVE-2024-56686 | same vendor as the line above | same change as the line above | Time to revision 10 days |
| 2025-01-07 | same kind of change as the line above | CVE-2024-56762 | same vendor as the line above | same change as the line above | Time to revision 1 days |
| Mon 6 Jan 2025· 1 change | |||||
| 2025-01-06 | Record state changed | CVE-2024-26929 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 251 days |
| Thu 19 Dec 2024· 10 changes | |||||
| 2024-12-195 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 115 to 260 days | |
| 2024-12-19 | same kind of change as the line above | CVE-2024-26848 | same vendor as the line above | same change as the line above | Time to revision 246 days |
| 2024-12-19 | same kind of change as the line above | CVE-2024-36885 | same vendor as the line above | same change as the line above | Time to revision 203 days |
| 2024-12-19 | same kind of change as the line above | CVE-2024-41024 | same vendor as the line above | same change as the line above | Time to revision 143 days |
| 2024-12-19 | same kind of change as the line above | CVE-2024-42116 | same vendor as the line above | same change as the line above | Time to revision 142 days |
| 2024-12-19 | same kind of change as the line above | CVE-2024-43903 | same vendor as the line above | same change as the line above | Time to revision 115 days |
| 2024-12-19 | same kind of change as the line above | CVE-2024-35928 | same vendor as the line above | same change as the line above | Time to revision 214 days |
| 2024-12-19 | same kind of change as the line above | CVE-2024-26713 | same vendor as the line above | same change as the line above | Time to revision 260 days |
| 2024-12-19 | same kind of change as the line above | CVE-2024-26720 | same vendor as the line above | same change as the line above | Time to revision 260 days |
| 2 more rows in this change are not listed here. Open all 10 rows → | |||||
| Thu 12 Dec 2024· 3 changes | |||||
| 2024-12-122 commits | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row. | Time to revision 17 to 52 days | |
| 2024-12-12 | same kind of change as the line above | CVE-2024-50089 | same vendor as the line above | same change as the line above | Time to revision 37 days |
| 2024-12-12 | same kind of change as the line above | CVE-2024-53102 | same vendor as the line above | same change as the line above | Time to revision 17 days |
| 2024-12-12 | same kind of change as the line above | CVE-2024-50018 | same vendor as the line above | same change as the line above | Time to revision 52 days |
| Thu 28 Nov 2024· 2 changes | |||||
| 2024-11-28 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 9 to 19 days | |
| 2024-11-28 | same kind of change as the line above | CVE-2024-50228 | same vendor as the line above | same change as the line above | Time to revision 19 days |
| 2024-11-28 | same kind of change as the line above | CVE-2024-53054 | same vendor as the line above | same change as the line above | Time to revision 9 days |
| Mon 11 Nov 2024· 1 change | |||||
| 2024-11-11 | Record state changed | CVE-2024-50219 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 2 days |
| Sun 10 Nov 2024· 1 change | |||||
| 2024-11-10 | Record state changed | CVE-2024-49993 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 20 days |
| Sat 9 Nov 2024· 1 change | |||||
| 2024-11-09 | Record state changed | CVE-2024-44952 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 66 days |
| Tue 29 Oct 2024· 1 change | |||||
| 2024-10-29 | Record state changed | CVE-2024-43885 | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 64 days |
| Wed 23 Oct 2024· 2 changes | |||||
| 2024-10-23 | Record state changed | whole record Linux | stated at publication PUBLISHED, now states REJECTED | Time to revision 2 days | |
| 2024-10-23 | same kind of change as the line above | CVE-2024-47725 | same vendor as the line above | same change as the line above | Time to revision 2 days |
| 2024-10-23 | same kind of change as the line above | CVE-2024-47755 | same vendor as the line above | same change as the line above | Time to revision 2 days |
Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. 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 →