Skip to content

Every fix version that moved

What a record said when it was published, what it says now, and the commit that changed it.

20 refused changes behind one line · newest firstCSVJSONRSS

SinceClear the filter
ChangedSourceRows

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.

One change, in full: Fix version moved: 6.19.1 → 7.0 from linux. The same change in 20 CVE records. Back to the ledger

Rows we checked and refused, counted nowhere of "Fix version moved", newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
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 changedDays 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.
2026-04-13CVE-2025-71229
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2025-71230
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2025-71231
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2025-71232
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2025-71233
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2025-71234
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2025-71235
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2025-71236
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2025-71237
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23220
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23221
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23222
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23223
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23224
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23225
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23226
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23227
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23228
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23229
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown
2026-04-13CVE-2026-23230
linuxlinux
stated at publication 6.19.1, 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.1 still holdsDuration unknown

This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller.

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 →