Skip to content

Record state changed

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

17 changes behind one line · newest firstCSVJSONRSS

SinceClear the filter

One change, in full: Record state changed: PUBLISHED → REJECTED. The same change in 17 CVE records. Back to the ledger

Counted changes of "Record state changed", 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.
2026-03-23CVE-2026-22173
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-28455
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-28483
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32012
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32047
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32066
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32900
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32901
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32902
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32903
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32904
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32907
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32908
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32909
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32910
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32911
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days
2026-03-23CVE-2026-32912
whole record
VulnCheck
stated at publication PUBLISHED, now states REJECTEDTime to revision 0 days

This kind is counted once per CVE record, so changes and records are the same number here.

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 →