Skip to content

Record state changed

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

35 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Record state changed" published by VulDB, 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 changedDays 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-25CVE-2026-78154
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 1 days
Thu 18 Jun 2026· 1 change
2026-06-18CVE-2025-15603
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 100 days
Mon 2 Feb 2026· 3 changes
2026-02-02
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 28 to 31 days
2026-02-02CVE-2025-15427same vendor as the line abovesame change as the line aboveTime to revision 31 days
2026-02-02CVE-2025-15446same vendor as the line abovesame change as the line aboveTime to revision 28 days
2026-02-02CVE-2025-15447same vendor as the line abovesame change as the line aboveTime to revision 28 days
Thu 8 Jan 2026· 1 change
2026-01-08CVE-2025-9173
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 141 days
Mon 3 Nov 2025· 5 changes
2025-11-032 commits
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDBranches and original-value intervals are stated on each row.Time to revision 8 to 87 days
2025-11-03CVE-2025-8733same vendor as the line abovesame change as the line aboveTime to revision 87 days
2025-11-03CVE-2025-8734same vendor as the line abovesame change as the line aboveTime to revision 87 days
2025-11-03CVE-2025-12198same vendor as the line abovesame change as the line aboveTime to revision 8 days
2025-11-03CVE-2025-12199same vendor as the line abovesame change as the line aboveTime to revision 8 days
2025-11-03CVE-2025-12200same vendor as the line abovesame change as the line aboveTime to revision 8 days
Sat 2 Aug 2025· 1 change
2025-08-02CVE-2025-8263
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 5 days
Mon 5 May 2025· 2 changes
2025-05-05
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 21 days
2025-05-05CVE-2025-3551same vendor as the line abovesame change as the line aboveTime to revision 21 days
2025-05-05CVE-2025-3552same vendor as the line abovesame change as the line aboveTime to revision 21 days
Tue 22 Apr 2025· 4 changes
2025-04-22
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 29 days
2025-04-22CVE-2025-2721same vendor as the line abovesame change as the line aboveTime to revision 29 days
2025-04-22CVE-2025-2722same vendor as the line abovesame change as the line aboveTime to revision 29 days
2025-04-22CVE-2025-2723same vendor as the line abovesame change as the line aboveTime to revision 29 days
2025-04-22CVE-2025-2724same vendor as the line abovesame change as the line aboveTime to revision 29 days
Mon 7 Apr 2025· 1 change
2025-04-07CVE-2025-2971
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 8 days
Fri 4 Apr 2025· 8 changes
2025-04-04
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 4 days
2025-04-04CVE-2025-2964same vendor as the line abovesame change as the line aboveTime to revision 4 days
2025-04-04CVE-2025-2965same vendor as the line abovesame change as the line aboveTime to revision 4 days
2025-04-04CVE-2025-2966same vendor as the line abovesame change as the line aboveTime to revision 4 days
2025-04-04CVE-2025-2967same vendor as the line abovesame change as the line aboveTime to revision 4 days
2025-04-04CVE-2025-2968same vendor as the line abovesame change as the line aboveTime to revision 4 days
2025-04-04CVE-2025-2969same vendor as the line abovesame change as the line aboveTime to revision 4 days
2025-04-04CVE-2025-2970same vendor as the line abovesame change as the line aboveTime to revision 4 days
2025-04-04CVE-2025-2972same vendor as the line abovesame change as the line aboveTime to revision 4 days
Thu 3 Apr 2025· 1 change
2025-04-03CVE-2025-2963
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 4 days
Thu 27 Mar 2025· 1 change
2025-03-27CVE-2025-2720
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 2 days
Tue 14 Jan 2025· 1 change
2025-01-14CVE-2024-13131
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 9 days
Mon 27 May 2024· 1 change
2024-05-27CVE-2024-3205
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 55 days
Thu 25 Apr 2024· 1 change
2024-04-25CVE-2024-0713
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 97 days
Mon 9 Oct 2023· 2 changes
2023-10-09
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 52 to 198 days
2023-10-09CVE-2023-1632same vendor as the line abovesame change as the line aboveTime to revision 198 days
2023-10-09CVE-2023-4413same vendor as the line abovesame change as the line aboveTime to revision 52 days
Sat 7 Oct 2023· 1 change
2023-10-07CVE-2023-5312
whole record
VulDB
stated at publication PUBLISHED, now states REJECTEDTime to revision 2 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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
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 →