Every fix version that moved
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.28000.2269 → 10.0.28000.2525 from microsoft. The same change in 191 CVE records. Back to the ledger
| 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. |
|---|---|---|---|---|
| 2026-07-22 | CVE-2026-33842 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-34328 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-34346 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-34348 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-34349 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-40378 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-40422 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-41087 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-42900 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-42975 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-42982 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-42990 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-44800 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-44806 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-48571 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49162 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49164 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49165 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49166 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49168 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49170 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49171 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49172 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49173 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49174 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49175 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49176 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49177 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49178 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49180 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49183 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49184 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49783 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49784 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49787 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49788 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49789 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49791 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49792 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49793 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49794 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49795 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49796 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49797 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49798 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49799 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49800 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49801 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49802 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49803 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49805 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49806 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49807 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-49808 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50293 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50294 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50295 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50297 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50298 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50299 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50300 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50302 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50303 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50305 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50306 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50307 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50308 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50309 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50310 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50311 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50312 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50313 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50315 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50316 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50317 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50321 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50322 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50323 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50325 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50326 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50327 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50329 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50330 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50331 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50332 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50333 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50334 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50335 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50336 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50337 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50339 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50340 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50342 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50343 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50344 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50345 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50346 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50347 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50348 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
| 2026-07-22 | CVE-2026-50350 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2525Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 8.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 8 days |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller.
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 →