All changesmicrosoftas of 2026-09-07
CVE-2025-60710
microsoftwindows 11 version 25h2cve.org →this looks wrong →
In CISA KEVlisted 2026-04-13federal fix was due 2026-04-27known ransomware use
Where you stand
Add ?v=your.version to this URL to mark where you stand.
stated at publication stated today
- windows 11 version 25h2from 10.0.26200.0
Record history
3 dated edit eventsPublished
- fixed from 10.0.26200.7171 · windows 11 version 25h2
- 3 products named later, not at publication
28 days between eventsFix version raisedSource 79eef2e — commit 79eef2eb8f37 in the CVE catalog
- fixed from 10.0.26200.7171, now fixed from 10.0.26200.7462windows 11 version 25h2
- 3 productsnot namedwindows 11 version 24h2, windows server 2025and 1 more
125 days between eventsAdded to CISA KEVSource 2f2f162 — commit 2f2f162e2618 in the CISA KEV
- Not listedListed 2026-04-13
123 days between eventsRansomware use confirmeddated by our sync, not CISASource 9f0c5cb — commit 9f0c5cb0ba6c in the CISA KEV
- BeforeUnknownAfterKnownWindows
24 days to snapshotSnapshot
- fixed from 10.0.26200.7462 · windows 11 version 25h2
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.
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-2025-60710. 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 f5f9fc6fd7dc. 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.