Skip to content
patchdrift.
snapshot 2026-09-07

All changesmicrosoftas of 2026-09-07

CVE-2026-32202

microsoftwindows 10 version 1607cve.org →this looks wrong →

In CISA KEVlisted 2026-04-28federal fix was due 2026-05-12

Record history

2 dated edit events

  1. Published

    • 18 release branches, each stating a fix version
    14 days between events

  2. Added to CISA KEVSource f4fae16 — commit f4fae1604a81 in the CISA KEV

    • Not listedListed 2026-04-28
    108 days between events

  3. Fix version raisedSource 9f8acf2 — commit 9f8acf231611 in the CVE catalog

    • fixed from 10.0.14393.9060, now fixed from 10.0.14393.9339windows 10 version 1607, windows server 2016 and 1 more
    • fixed from 10.0.17763.8644, now fixed from 10.0.17763.9020windows 10 version 1809, windows server 2019 and 1 more
    • fixed from 10.0.19044.7184, now fixed from 10.0.19044.7548windows 10 version 21h2
    • and 11 more branches in this commit, drawn on the ladder
    24 days to snapshot

  4. Snapshot

    • 18 release branches, every one moved since publication

Where you stand

Add ?v=your.version to this URL to mark where you stand.

stated at publication stated todayall 18 branches Revised after 122 days

  1. windows 10 version 1607from 10.0.14393.0
    microsoft windows 10 version 1607: at publication fixed from 10.0.14393.9060; now fixed from 10.0.14393.9339; the first revision was after 122 days.10.0.14393.906010.0.14393.9339
  2. windows 10 version 1809from 10.0.17763.0
    microsoft windows 10 version 1809: at publication fixed from 10.0.17763.8644; now fixed from 10.0.17763.9020; the first revision was after 122 days.10.0.17763.864410.0.17763.9020
  3. windows 10 version 21h2from 10.0.19044.0
    microsoft windows 10 version 21h2: at publication fixed from 10.0.19044.7184; now fixed from 10.0.19044.7548; the first revision was after 122 days.10.0.19044.718410.0.19044.7548
  4. windows 10 version 22h2from 10.0.19045.0
    microsoft windows 10 version 22h2: at publication fixed from 10.0.19045.7184; now fixed from 10.0.19045.7548; the first revision was after 122 days.10.0.19045.718410.0.19045.7548
  5. windows 11 version 23h2from 10.0.22631.0
    microsoft windows 11 version 23h2: at publication fixed from 10.0.22631.6936; now fixed from 10.0.22631.7376; the first revision was after 122 days.10.0.22631.693610.0.22631.7376
  6. windows 11 version 25h2from 10.0.26200.0
    microsoft windows 11 version 25h2: at publication fixed from 10.0.26200.8246; now fixed from 10.0.26200.8875; the first revision was after 122 days.10.0.26200.824610.0.26200.8875
  7. windows 11 version 26h1from 10.0.28000.0
    microsoft windows 11 version 26h1: at publication fixed from 10.0.28000.1836; now fixed from 10.0.28000.2525; the first revision was after 122 days.10.0.28000.183610.0.28000.2525
  8. windows server 2012from 6.2.9200.0
    microsoft windows server 2012: at publication fixed from 6.2.9200.26026; now fixed from 6.2.9200.26226; the first revision was after 122 days.6.2.9200.260266.2.9200.26226
  9. windows server 2012 (server core installation)from 6.2.9200.0
    microsoft windows server 2012 (server core installation): at publication fixed from 6.2.9200.26026; now fixed from 6.2.9200.26226; the first revision was after 122 days.6.2.9200.260266.2.9200.26226
  10. windows server 2012 r2from 6.3.9600.0
    microsoft windows server 2012 r2: at publication fixed from 6.3.9600.23132; now fixed from 6.3.9600.23291; the first revision was after 122 days.6.3.9600.231326.3.9600.23291
  11. windows server 2012 r2 (server core installation)from 6.3.9600.0
    microsoft windows server 2012 r2 (server core installation): at publication fixed from 6.3.9600.23132; now fixed from 6.3.9600.23291; the first revision was after 122 days.6.3.9600.231326.3.9600.23291
  12. windows server 2016from 10.0.14393.0
    microsoft windows server 2016: at publication fixed from 10.0.14393.9060; now fixed from 10.0.14393.9339; the first revision was after 122 days.10.0.14393.906010.0.14393.9339
  13. windows server 2016 (server core installation)from 10.0.14393.0
    microsoft windows server 2016 (server core installation): at publication fixed from 10.0.14393.9060; now fixed from 10.0.14393.9339; the first revision was after 122 days.10.0.14393.906010.0.14393.9339
  14. windows server 2019from 10.0.17763.0
    microsoft windows server 2019: at publication fixed from 10.0.17763.8644; now fixed from 10.0.17763.9020; the first revision was after 122 days.10.0.17763.864410.0.17763.9020
  15. windows server 2019 (server core installation)from 10.0.17763.0
    microsoft windows server 2019 (server core installation): at publication fixed from 10.0.17763.8644; now fixed from 10.0.17763.9020; the first revision was after 122 days.10.0.17763.864410.0.17763.9020
  16. windows server 2022from 10.0.20348.0
    microsoft windows server 2022: at publication fixed from 10.0.20348.5020; now fixed from 10.0.20348.5386; the first revision was after 122 days.10.0.20348.502010.0.20348.5386
  17. windows server 2025from 10.0.26100.0
    microsoft windows server 2025: at publication fixed from 10.0.26100.32690; now fixed from 10.0.26100.33158; the first revision was after 122 days.10.0.26100.3269010.0.26100.33158
  18. windows server 2025 (server core installation)from 10.0.26100.0
    microsoft windows server 2025 (server core installation): at publication fixed from 10.0.26100.32690; now fixed from 10.0.26100.33158; the first revision was after 122 days.10.0.26100.3269010.0.26100.33158

Check your tickets

Add your patched version to compare it with the recorded boundary.

One per line · up to 500 IDs

Versions & supported formats

Add a patched version beside a CVE to compare it. GHSA versions are not compared. Product names are also supported. Results include a watchlist link, RSS and JSON.

Privacy & sharingData & methodology

Change cards link to the source commit. Compare CVE values with the first mirrored record and KEV values with the preceding catalog snapshot. The full recipe →

Data coverage & methodology

CVE values compare the first mirrored record with later source states. Initial records may have been backfilled after publication. KEV events compare consecutive catalog snapshots. Dates identify the reported value’s first observed appearance; earlier intermediate revisions may exist. Only counted rows contribute to totals. as of the 2026-09-07 snapshot.

On the ladder, positions are ordinal: the gap says the boundary moved, not by how much; the strings say the values. Its shade is time to the first recorded revision, from same-day (palest) to over a year. Only branches whose boundary moved are shipped, so a branch that held is not drawn.

Not checked: a record published before 2023 cannot have its state at publication recovered, so the CVE-record checks never compared it. For such a record, silence on this page means it was not looked at, not that it held.

Not checked: a CISA KEV listing added before 2025-01-27 was never seen changing, so a record that has been in KEV for years carries no listing node here. A missing KEV node is not evidence that CISA has not listed it.

The GitHub Advisory Database was read and carries no changed advisory naming CVE-2026-32202. An advisory is an entry in the GitHub Advisory Database, the GHSA page a Dependabot alert links to. It is reached from a CVE id only when the advisory names that CVE id itself, and many advisories name none. So no advisory here means none was found among the advisories that name one of these ids. It does not mean there is nothing to find.

How every one of these figures is measured, in full →

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.

Shipped snapshot computed 2026-09-07 from catalog commit 1f78fd2580c1. Real findings, not live ones: records amended since are not reflected. A later fix version is evidence that the record changed, not evidence that the first fix was incomplete.