Skip to content

Every change, newest first

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

33 refused changes behind one line · newest firstCSVJSONRSS

Since
ChangedSourceRows

These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.

One change, in full: Fix version moved: 10.0.22000.1574 → 10.0.22621.1574 from microsoft. The same change in 33 CVE records. Back to the ledger

Rows we checked and refused, counted nowhere, 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.KindRecord 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 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.
2023-08-23Fix version movedCVE-2023-21684
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21685
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21686
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21687
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21688
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21689
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21690
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21691
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21692
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21693
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21694
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21695
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21700
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21701
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21702
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21797
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21798
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21799
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21801
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21802
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21804
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21805
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21811
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21812
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21813
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21816
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21817
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21818
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21819
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21820
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21822
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-21823
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189
2023-08-23Fix version movedCVE-2023-23376
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1574, now states 10.0.22621.1574Release branch starts at 10.0.0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 189

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 or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.

Data sources and quality

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 →

Check my CVEs against these changes →