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.

7 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
Counted changes of "Fix version moved" from GitLab, 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.
Mon 30 Mar 2026· 1 record change
2026-03-30CVE-2025-13611
gitlabgitlab
stated at publication 18.6.1, now states 18.6.3Release branch starts at 18.6.Days to revision 124
Thu 9 Jan 2025· 2 record changes
2025-01-09CVE-2025-0194
gitlabgitlab
stated at publication 17.5.1, now states 17.5.5Release branch starts at 17.4.same dayDays to revision 0
2025-01-09CVE-2025-0194
gitlabgitlab
stated at publication 17.6.1, now states 17.6.3Release branch starts at 17.6.same dayDays to revision 0
Fri 6 Dec 2024· 2 record changes
2024-12-06CVE-2024-9633
gitlabgitlab
stated at publication 17.3.7, now states 17.4.2Release branch starts at 16.3.Days to revision 22
2024-12-06CVE-2024-9633
gitlabgitlab
stated at publication 17.5.2, now states 17.5.4Release branch starts at 17.5.Days to revision 22
Mon 26 Feb 2024· 2 record changes
2024-02-26CVE-2023-6736
gitlabgitlab
stated at publication 16.6.7, now states 16.7.6Release branch starts at 11.3.Days to revision 19
2024-02-26CVE-2023-6736
gitlabgitlab
stated at publication 16.8.2, now states 16.8.3Release branch starts at 16.8.Days to revision 19

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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

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 →

Check my CVEs against these changes →