Every change, newest first
These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.
| Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin. | 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. |
|---|---|---|---|---|---|
| Tue 1 Sep 2026· 1 change | |||||
| 2026-09-01 | Forensic triage now required | CVE-2026-53362 | LinuxKernel CISA KEV | stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirement | Time to revision 5 days |
| Wed 29 Jul 2026· 1 change | |||||
| 2026-07-29 | Affected range extended | CVE-2023-1829 | linuxlinux kernel Google | stated at publication 6.2, now states 6.3.0Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.2 still holds | Duration unknown |
| Sun 14 Jun 2026· 59 changes | |||||
| 2026-06-14 | Fix version moved | linuxlinux | stated at publication 7.0.1, now states 7.1Release branch starts at *.not counted: Another branch advanced | Duration unknown | |
| 2026-06-14 | same kind of change as the line above | CVE-2026-31532 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | Duration unknown |
| 2026-06-14 | same kind of change as the line above | CVE-2026-31574 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | Duration unknown |
| 2026-06-14 | same kind of change as the line above | CVE-2026-31575 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | Duration unknown |
| 2026-06-14 | same kind of change as the line above | CVE-2026-31576 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | Duration unknown |
| 2026-06-14 | same kind of change as the line above | CVE-2026-31577 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | Duration unknown |
| 2026-06-14 | same kind of change as the line above | CVE-2026-31578 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | Duration unknown |
| 2026-06-14 | same kind of change as the line above | CVE-2026-31579 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | Duration unknown |
| 2026-06-14 | same kind of change as the line above | CVE-2026-31580 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.1 still holds | Duration unknown |
| 49 more rows in this change are not listed here. Open all 57 rows → | |||||
| 2026-06-14 | Fix version moved | linuxlinux | stated at publication 7.0.3, now states 7.1Release branch starts at *.not counted: Another branch advanced | Duration unknown | |
| 2026-06-14 | same kind of change as the line above | CVE-2026-31786 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.3 still holds | Duration unknown |
| 2026-06-14 | same kind of change as the line above | CVE-2026-31787 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 7.0.3 still holds | Duration unknown |
| Mon 13 Apr 2026· 21 changes | |||||
| 2026-04-13 | Fix version moved | linuxlinux | stated at publication 6.19.1, now states 7.0Release branch starts at *.not counted: Another branch advanced | Duration unknown | |
| 2026-04-13 | same kind of change as the line above | CVE-2025-71229 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.19.1 still holds | Duration unknown |
| 2026-04-13 | same kind of change as the line above | CVE-2025-71230 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.19.1 still holds | Duration unknown |
| 2026-04-13 | same kind of change as the line above | CVE-2025-71231 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.19.1 still holds | Duration unknown |
| 2026-04-13 | same kind of change as the line above | CVE-2025-71232 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.19.1 still holds | Duration unknown |
| 2026-04-13 | same kind of change as the line above | CVE-2025-71233 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.19.1 still holds | Duration unknown |
| 2026-04-13 | same kind of change as the line above | CVE-2025-71234 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.19.1 still holds | Duration unknown |
| 2026-04-13 | same kind of change as the line above | CVE-2025-71235 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.19.1 still holds | Duration unknown |
| 2026-04-13 | same kind of change as the line above | CVE-2025-71236 | same vendor as the line above | same change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.19.1 still holds | Duration unknown |
| 12 more rows in this change are not listed here. Open all 20 rows → | |||||
| 2026-04-13 | Fix version moved | CVE-2026-31788 | linuxlinux | stated at publication 6.19.10, now states 7.0Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.19.10 still holds | Duration unknown |
| Mon 1 Dec 2025· 1 change | |||||
| 2025-12-01 | Fix version moved | CVE-2025-40084 | linuxlinux | stated at publication 6.17.6, now states 6.18Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.17.6 still holds | Duration unknown |
| Sat 11 Oct 2025· 1 change | |||||
| 2025-10-11 | Fix version moved | CVE-2025-40364 | linuxlinux | stated at publication 6.6.78, now states 6.14Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.6.78 still holds | Duration unknown |
| Fri 10 Oct 2025· 2 changes | |||||
| 2025-10-10 | Fix version moved | CVE-2025-21988 | linuxlinux | stated at publication 6.13.8, now states 6.14Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.13.8 still holds | Duration unknown |
| 2025-10-10 | Fix version moved | CVE-2023-53642 | linuxlinux | stated at publication 6.1.29, now states 6.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.1.29 still holds | Duration unknown |
| Mon 29 Sep 2025· 1 change | |||||
| 2025-09-29 | Fix version moved | CVE-2025-40300 | linuxlinux | stated at publication 6.16.7, now states 6.17Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.16.7 still holds | Duration unknown |
| Mon 28 Jul 2025· 1 change | |||||
| 2025-07-28 | Fix version moved | CVE-2025-38001 | linuxlinux | stated at publication 6.15.1, now states 6.16Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.15.1 still holds | Duration unknown |
| Mon 13 May 2024· 1 change | |||||
| 2024-05-13 | Fix version moved | CVE-2024-26817 | linuxlinux | stated at publication 6.8.6, now states 6.9Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.8.6 still holds | Duration unknown |
| Mon 11 Mar 2024· 1 change | |||||
| 2024-03-11 | Fix version moved | CVE-2024-26602 | linuxlinux | stated at publication 6.7.6, now states 6.8Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
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 →