Every fix version that moved
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. | 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. |
|---|---|---|---|---|
| Sun 14 Jun 2026· 59 record changes | ||||
| 2026-06-14 | linuxlinux | stated at publication 7.0.1, now states 7.1Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-06-14 | 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 | not dated |
| 2026-06-14 | 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 | not dated |
| 2026-06-14 | 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 | not dated |
| 2026-06-14 | 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 | not dated |
| 2026-06-14 | 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 | not dated |
| 2026-06-14 | 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 | not dated |
| 2026-06-14 | 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 | not dated |
| 2026-06-14 | 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 | not dated |
| 49 more rows in this change are not listed here. Open all 57 rows → | ||||
| 2026-06-14 | linuxlinux | stated at publication 7.0.3, now states 7.1Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-06-14 | 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 | not dated |
| 2026-06-14 | 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 | not dated |
| Mon 13 Apr 2026· 21 record changes | ||||
| 2026-04-13 | linuxlinux | stated at publication 6.19.1, now states 7.0Release branch starts at *.not counted: Another branch advanced | not dated | |
| 2026-04-13 | 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 | not dated |
| 2026-04-13 | 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 | not dated |
| 2026-04-13 | 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 | not dated |
| 2026-04-13 | 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 | not dated |
| 2026-04-13 | 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 | not dated |
| 2026-04-13 | 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 | not dated |
| 2026-04-13 | 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 | not dated |
| 2026-04-13 | 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 | not dated |
| 12 more rows in this change are not listed here. Open all 20 rows → | ||||
| 2026-04-13 | 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 | not dated |
| Mon 1 Dec 2025· 1 record change | ||||
| 2025-12-01 | 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 | not dated |
| Sat 11 Oct 2025· 1 record change | ||||
| 2025-10-11 | 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 | not dated |
| Fri 10 Oct 2025· 2 record changes | ||||
| 2025-10-10 | 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 | not dated |
| 2025-10-10 | 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 | not dated |
| Mon 29 Sep 2025· 1 record change | ||||
| 2025-09-29 | 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 | not dated |
| Mon 28 Jul 2025· 1 record change | ||||
| 2025-07-28 | 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 | not dated |
| Mon 13 May 2024· 1 record change | ||||
| 2024-05-13 | 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 | not dated |
| Mon 11 Mar 2024· 1 record change | ||||
| 2024-03-11 | 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 | not dated |
This kind is counted once per record, product and release branch, so one record that moved the boundary on four branches counts four times and the number of records behind these changes is smaller. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.
Data sources and quality
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 →