Every change, newest first

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

4 changes · newest first · grouped by dayCSV JSON RSS

PublisherPublishedChangedSourceRows

Counted changes published by f5, 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.	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.
Wed 4 Mar 2026· 1 record change
2026-03-04	Fix version moved	CVE-2025-53868	f5big-ip	stated at publication 17.1.3, now states 17.1.3.1Release branch starts at 17.1.0.	Days to revision 140
Wed 4 Feb 2026· 1 record change
2026-02-04	CVSS base score changed	CVE-2025-60013	whole record f5	stated at publication 5.7, now states 4.6CVSS v3.1 · base scoreMediumMedium	Days to revision 112
Thu 28 Aug 2025· 1 record change
2025-08-28	CVSS base score changed	CVE-2024-23306	whole record f5	stated at publication 4.4, now states 7.1CVSS v3.1 · base scoreMediumHigh	Days to revision 561
Tue 3 Oct 2023· 1 record change
2023-10-03	CVSS base score changed	CVE-2023-22283	whole record f5	stated at publication 6.3, now states 6.5CVSS v3.1 · base scoreMediumMedium	Days to revision 244

Rows, not records: a moved fix version or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. 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.

3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 12:43 UTC · scroll for earlierfewermore

Every kind of change

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

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 →