Every change, newest first

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

140 changes · newest first · grouped by dayCSV JSON RSS

PublisherPublishedChangedSourceRows

Counted changes published by GitHub_M, 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.
Fri 25 Aug 2023· 2 changes
2023-08-25	CVSS base score changed	Show all 2 CVE records in this change: CVSS base score changed: 6.3 → 5.5Hide the 2 CVE records in this change: CVSS base score changed: 6.3 → 5.5	whole record GitHub_M	stated at publication 6.3, now states 5.5CVSS v3.1 · base scoreMediumMedium	Time to revision 0 days
2023-08-25	same kind of change as the line above	CVE-2023-40036	same vendor as the line above	same change as the line above	Time to revision 0 days
2023-08-25	same kind of change as the line above	CVE-2023-40164	same vendor as the line above	same change as the line above	Time to revision 0 days
Thu 6 Jul 2023· 1 change
2023-07-06	Record state changed	CVE-2023-35935	whole record GitHub_M	stated at publication PUBLISHED, now states REJECTED	Time to revision 3 days
Thu 29 Jun 2023· 1 change
2023-06-29	Record state changed	CVE-2023-35170	whole record GitHub_M	stated at publication PUBLISHED, now states REJECTED	Time to revision 3 days
Wed 14 Jun 2023· 2 changes
2023-06-14	CVSS base score changed	CVE-2023-34251	whole record GitHub_M	stated at publication 9.1, now states 10.0CVSS v3.1 · base scoreCriticalCritical	Time to revision 0 days
2023-06-14	CVSS base score changed	CVE-2023-34252	whole record GitHub_M	stated at publication 7.2, now states 8.8CVSS v3.1 · base scoreHighHigh	Time to revision 0 days
Wed 17 May 2023· 1 change
2023-05-17	Product added	CVE-2023-27482	home-assistant GitHub_M	not named as affected at publication, now names supervisor	Time to revision 71 days
Wed 10 May 2023· 1 change
2023-05-10	Product added	CVE-2023-25568	ipfs GitHub_M	not named as affected at publication, now names boxo	Time to revision 1 days
Thu 27 Apr 2023· 1 change
2023-04-27	Record state changed	CVE-2023-30842	whole record GitHub_M	stated at publication PUBLISHED, now states REJECTED	Duration unknown
Mon 3 Apr 2023· 1 change
2023-04-03	CVSS base score changed	CVE-2023-28836	whole record GitHub_M	stated at publication 4.4, now states 6.4CVSS v3.1 · base scoreMediumMedium	Time to revision 1 days

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.

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 →