All changesmicrosoftas of 2026-09-07
CVE-2024-26211
microsoftwindows 10 version 1809cve.org →this looks wrong →
Where you stand
| Branch | Fix stated at publication | Fix stated today | Stood |
|---|---|---|---|
| windows 10 version 1809from 10.0.0 | at publication 10.0.17763.5696 | today 10.0.17763.5820 | stood 35 days |
Record history
2 dated edit eventsPublished
- fixed from 10.0.17763.5696 · windows 10 version 1809
35 days between eventsFix version raisedSource e82dcc9 — commit e82dcc91f585 in the CVE catalog
- fixed from 10.0.17763.5696, now fixed from 10.0.17763.5820windows 10 version 1809
231 days between eventsExcluded comparisonnot countedSource 72e71a7 — commit 72e71a77195c in the CVE catalog
- fixed from 10.0.10240.20596, now fixed from 10.0.10240.20651windows 10 version 1507
- fixed from 10.0.14393.6897, now fixed from 10.0.14393.6981windows 10 version 1607, windows server 2016 and 1 more
- fixed from 10.0.19044.4291, now fixed from 10.0.19044.4412windows 10 version 21h2
- and 10 more branches in this commit, listed under Where you stand
Filtered, not counted: the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched.
615 days to snapshotSnapshot
- fixed from 10.0.17763.5820 · windows 10 version 1809
Check your tickets
Add your patched version to compare it with the recorded boundary.
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.
15 rows marked filtered, not counted are on the rail and counted nowhere. 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.
Under Where you stand, only branches whose boundary moved are shipped, so a branch that held is not listed. Stood is days from publication to the first recorded revision of that branch.
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-2024-26211. 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 ed5547afbae2. 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.