Record state changed

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

24 changes · newest first · grouped by dayCSV JSON RSS

Counted changes of "Record state changed" published by Patchstack, 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.
Tue 25 Aug 2026· 1 change
2026-08-25	CVE-2026-73189	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 7 days
Fri 14 Aug 2026· 2 changes
2026-08-142 commits	Show all 2 CVE records in this change: Record state changed: PUBLISHED → REJECTEDHide the 2 CVE records in this change: Record state changed: PUBLISHED → REJECTED	whole record Patchstack	stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row.	Time to revision 1 days
2026-08-14	CVE-2026-73188	same vendor as the line above	same change as the line above	Time to revision 1 days
2026-08-14	CVE-2026-28184	same vendor as the line above	same change as the line above	Time to revision 1 days
Thu 6 Aug 2026· 1 change
2026-08-06	CVE-2026-28183	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 0 days
Thu 11 Jun 2026· 1 change
2026-06-11	CVE-2026-27066	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 112 days
Wed 29 Apr 2026· 1 change
2026-04-29	CVE-2026-39660	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 21 days
Tue 21 Apr 2026· 1 change
2026-04-21	CVE-2026-39659	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 13 days
Mon 6 Apr 2026· 1 change
2026-04-06	CVE-2025-57958	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 196 days
Wed 18 Mar 2026· 1 change
2026-03-18	CVE-2023-47663	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 652 days
Tue 24 Feb 2026· 1 change
2026-02-24	CVE-2026-25412	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 5 days
Wed 4 Feb 2026· 1 change
2026-02-04	CVE-2026-24602	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 12 days
Mon 2 Feb 2026· 2 changes
2026-02-022 commits	Show all 2 CVE records in this change: Record state changed: PUBLISHED → REJECTEDHide the 2 CVE records in this change: Record state changed: PUBLISHED → REJECTED	whole record Patchstack	stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row.	Time to revision 536 to 609 days
2026-02-02	CVE-2024-34764	same vendor as the line above	same change as the line above	Time to revision 609 days
2026-02-02	CVE-2024-43275	same vendor as the line above	same change as the line above	Time to revision 536 days
Fri 9 Jan 2026· 1 change
2026-01-09	CVE-2026-0675	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 1 days
Mon 8 Dec 2025· 1 change
2025-12-08	CVE-2025-62893	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 43 days
Fri 21 Nov 2025· 1 change
2025-11-21	CVE-2025-62908	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 25 days
Thu 20 Nov 2025· 1 change
2025-11-20	CVE-2025-57901	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 59 days
Wed 22 Oct 2025· 1 change
2025-10-22	CVE-2025-53459	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 30 days
Thu 4 Sep 2025· 1 change
2025-09-04	CVE-2025-52709	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 69 days
Mon 14 Apr 2025· 1 change
2025-04-14	CVE-2025-32200	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 10 days
Wed 12 Mar 2025· 1 change
2025-03-12	CVE-2024-35173	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 299 days
Thu 12 Sep 2024· 1 change
2024-09-12	CVE-2024-38688	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 30 days
Tue 26 Mar 2024· 1 change
2024-03-26	CVE-2023-41696	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 0 days
Wed 20 Mar 2024· 1 change
2024-03-20	CVE-2023-47691	whole record Patchstack	stated at publication PUBLISHED, now states REJECTED	Time to revision 13 days

This kind is counted once per CVE record, so changes and records are the same number here. 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

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 →