Every change, newest first

Compare earlier and later source statements, with the dates and evidence behind each measured change.

5 record changes · 1 advisory changes · newest first · grouped by dayCSV JSON RSS

SinceKindVendorSortClear all

Showing changes seen on 2025-10-29. Every day

Counted changes changed on 2025-10-29, newest first, one line per change to a CVE record or a GHSA advisory, 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 or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together.	Vendor or package, 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 29 Oct 2025· 6 changes
2025-10-29	Ransomware use confirmed	CVE-2024-9474	Palo Alto NetworksPAN-OS CISA KEV	stated at publication Unknown, now states Known	Duration unknown
2025-10-29	Fix version moved	CVE-2025-41443	mattermostmattermost	stated at publication 10.5.11, now states 10.5.13Release branch starts at 10.5.0.	Time to revision 13 days
2025-10-29	Record state changed	CVE-2025-62516	whole record GitHub_M	stated at publication PUBLISHED, now states REJECTED	Time to revision 2 days
2025-10-29	Record state changed	CVE-2023-53293	whole record Linux	stated at publication PUBLISHED, now states REJECTED	Time to revision 43 days
2025-10-29	Record state changed	CVE-2025-62813	whole record mitre	stated at publication PUBLISHED, now states REJECTED	Time to revision 6 days
2025-10-29published 2025-08-20	Package added to advisory	GHSA-p72g-pv48-7w9xCVE-2025-54988	maven critical	not named as affected when the advisory was published, now names org.apache.tika:tika-parsers	Time to revision 70 days

Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

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

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 →