Every fix version that moved

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

9 changes behind one line · newest firstCSV JSON RSS

One change, in full: Fix version moved: 20.0 → 20.1 from world wide broadcast network. The same change in 9 CVE records. Back to the ledger

Counted changes of "Fix version moved" from world wide broadcast network, 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 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.
2025-12-19	CVE-2025-34441	world wide broadcast networkavideo VulnCheck	stated at publication 20.0, now states 20.1Release branch starts at 0.	Time to revision 2 days
2025-12-19	CVE-2025-34442	world wide broadcast networkavideo VulnCheck	stated at publication 20.0, now states 20.1Release branch starts at 0.	Time to revision 2 days
2025-12-19	CVE-2025-34440	world wide broadcast networkavideo VulnCheck	stated at publication 20.0, now states 20.1Release branch starts at 0.	Time to revision 2 days
2025-12-19	CVE-2025-34439	world wide broadcast networkavideo VulnCheck	stated at publication 20.0, now states 20.1Release branch starts at 0.	Time to revision 2 days
2025-12-19	CVE-2025-34434	world wide broadcast networkavideo VulnCheck	stated at publication 20.0, now states 20.1Release branch starts at 0.	Time to revision 2 days
2025-12-19	CVE-2025-34436	world wide broadcast networkavideo VulnCheck	stated at publication 20.0, now states 20.1Release branch starts at 0.	Time to revision 2 days
2025-12-19	CVE-2025-34435	world wide broadcast networkavideo VulnCheck	stated at publication 20.0, now states 20.1Release branch starts at 0.	Time to revision 2 days
2025-12-19	CVE-2025-34437	world wide broadcast networkavideo VulnCheck	stated at publication 20.0, now states 20.1Release branch starts at 0.	Time to revision 2 days
2025-12-19	CVE-2025-34438	world wide broadcast networkavideo VulnCheck	stated at publication 20.0, now states 20.1Release branch starts at 0.	Time to revision 2 days

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.

Every kind of change

All kinds

Each bar filters the ledger to that kind, and counts what it would show under the filters already on. Two units, one length scale, never a total.

To a CVE record or a KEV entry

To a GitHub advisory

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 →