Nine Microsoft case files sit on this blog. One rule connects them. The patch's scope equals the advisory's title, and everything the researcher documented outside the title is still there on Patch Tuesday afternoon.
The Nefarious Plan of Microsoft
Microsoft fixed the specific instance.
That sentence runs through CLFS: Ransomware's Favorite Kernel Driver five times, once for each of the five in-the-wild CLFS kernel exploits Microsoft shipped a patch for between April 2022 and April 2025. The Common Log File System is a kernel driver every Windows machine ships with, and any local user can feed it a file that triggers the parser. The file ends with the line the thesis sentence sets up:
The fix keeps being the wrong scope.
Nine files later, this is no longer about one driver. The patch's scope equals the advisory's title. The attacker's entry point, the researcher's substrate, the primitive the file format exists to provide, the other three render paths, the audit tool that reads the wrong section of config, all of that is still there on Patch Tuesday afternoon. The researcher wrote it down. Microsoft read the title.
The title is where the patch stops
BlueHammer: What the Researcher Commented Out is a hundred kilobytes of exploit that assembles an RPC call into Defender, a batch oplock on a system DLL, an NT object namespace symlink, and a Cloud Files sync-provider freeze into a SAM database read at SYSTEM privilege. SAM holds every local user's password hash. Microsoft patched exactly one of the four primitives, the object namespace lookup in Defender's definition update code.
The patch closed the specific door the PoC walks through. The wall the door is cut into is unchanged.
The RPC interface still answers to any user process. The symlink syscall still works from standard user. The Cloud Files filter driver still blocks Defender when a fake sync provider refuses to validate. Three of the four primitives are untouched. The one that got touched is the one the advisory named.
CVE-2026-32202: The Trust Check Runs at the Click. The Coercion Runs at the Icon. is the Shell LNK zero-day Microsoft announced a fix for in April 2026. The fix adds a class named ControlPanelLinkSite that asks SmartScreen to vet the target before the shell launches it. SmartScreen is the reputation service that decides whether an executable is allowed to run. The verifier guards exactly one Windows API.
The trust verifier guards
ShellExecuteExW. The auth coercion never reachesShellExecuteExW.
The coercion fires when Explorer draws the icon. The user has not clicked anything. The hash is on the wire. The patched administrator owns a build where the folder listing is the attack surface.
CVE-2025-24054: The Two Verbs That Don't Trigger Are 'Open' and 'Execute' is the .library-ms shell descriptor file, an XML format whose URL element the Explorer handler resolves whenever Explorer renders the file. Microsoft's advisory predicted the bug would not be exploited on March 11, 2025. Eight days later it was in the wild in Poland and Romania. Thirty-seven days later it was on CISA's Known Exploited catalog. The forecast is still on the bulletin.
<simpleLocation><url>is what.library-msfiles do. The patch closes the selection trigger; the element remains.
There is a template behind that sentence. CVE-2025-33053 Was the WorkingDirectory Half. The Other Half Got a Documentation Edit. is the .URL file variant. The .URL format is an INI file with two directives that matter here, URL and WorkingDirectory. Microsoft fixed the WorkingDirectory directive, which almost nothing uses. The URL directive, which is the entire reason the format ships, Microsoft left alone. Will Dormann reported it. MSRC declined to issue a CVE and edited the Learn page from "the browser is launched" to "the handler application, typically the user's default web browser."
The URL= line is what
.URLfiles do. Microsoft will not assign a CVE to what.URLfiles do.
The documentation team conceded the behavior in prose. The CVE team declined to concede it in a database row.
CVE-2026-26128: Microsoft Titled It SMB. The Primitive Is DnsCache and the KDC Disagreeing About a Hostname. is the title where the pattern admits itself out loud. Microsoft published an advisory called "Windows SMB Server Elevation of Privilege" for a bug whose mechanism is that two Windows components call different Win32 normalization functions on the same hostname and get different answers. DnsCache, the Windows name resolver, decides whether a name refers to this machine. The Kerberos key distribution center, running in the same process tree, decides whether two service principal names refer to the same account. They disagree on circled Unicode letters. The domain controller authenticates to itself. The attacker relays the ticket.
The patch closes one of the answers.
Three of the four relay targets the public research names are unaffected by the patch. The README of the public PoC says it in one sentence: SMB relay is dead on patched hosts, the web enrollment endpoint for Microsoft's Certificate Services is not. The word "SMB" in the advisory title was the scope boundary.
CVE-2026-42897: EOMT Deploys to Outbound Rules. Health Checker Reads Inbound. is the same scope boundary one organizational layer out. An IIS rewrite rule can transform either incoming requests or outgoing responses. The emergency mitigation ships from microsoft/CSS-Exchange, installs a Content-Security-Policy via an outgoing rewrite rule, and names the rule EOMT OWA CSP - outbound because there is nowhere else the rule could live. The audit tool ships from microsoft/CSS-Exchange and reads three places. None of them are the outgoing section. Both tools are Microsoft's. Both were written by engineers who were correct about their own tool.
The verifier cannot tell a server that needs the mitigation from a server that already has it.
The reconciliation between the two tools did not happen inside the organization that owns both tools. The mitigation lives where the audit tool does not look because no one at Microsoft was responsible for checking whether the audit tool looked.
What this is not
I am not charging Microsoft with every file above. I am charging the scope decision.
Sandboxing the CLFS kernel parser is non-trivial engineering work. The CLFS file says so, and I agree. Redesigning the BLF object lifecycle to eliminate the use-after-free conditions touches subsystems other kernel code depends on. These are real costs. Microsoft pays them whichever way they decide.
The XSS fix in the April Exchange update is a real fix. OWA does not execute the attacker's payload after the patch lands. The audit tool bug is a separable claim. The patch is honest.
CVE-2010-0249: The KEV Deadline for Aurora Is a Census is the Operation Aurora use-after-free in Internet Explorer that Microsoft patched in nine days in January 2010, the first emergency out-of-band IE patch in modern Microsoft history. That cadence has not been bettered.
The CVE is sixteen years old. The patch is sixteen years old. The fourteen-day deadline is not for the patch.
The 2026 KEV listing is a census of agencies still running the product. The patch is fine. The product persists.
CVE-2025-47987: The CredSSP PoC Documents A Project That Does Not Exist is an authentication bug in the Windows protocol for passing credentials to remote services. Microsoft shipped the patch in July 2025. The public PoC that landed ten months later is a pile of three files generated by an author who never read the directory listing on the repo they published.
A CVE number was the seam.
That one is not on Microsoft. Random actors uploading placeholder repositories ten months after the patch are an ecosystem feature, not a vendor failure. For once, the vendor did what the vendor should do.
The charge is narrower. When a researcher writes down a primitive, the vendor's reply is the subset of that primitive they chose to fit on the bulletin.
Where the next file comes from
If you want to find the next Microsoft file on this blog before I write it, do not read Microsoft's patch notes. Read the paragraphs in each of the files above that enumerate the surface the current patch did not touch.
BlueHammer names the surface directly. The IMpService RPC interface has UUID c503f532-443a-4c69-8300-ccd1fbdb3839. It has methods other than the one the current PoC calls. The methods have not been audited against the object-namespace-symlink class in the post-patch world. Whichever method's code path next walks a redirectable path name is the next advisory.
CVE-2026-32202 names the other Shell render paths by category: tooltip resolution, preview pane thumbnail providers, infotip composition, property-handler walks. Each is a different code path Explorer runs when it draws a folder on screen. None is guarded by the ControlPanelLinkSite verifier.
CVE-2026-26128 names the count. At least four different "is this hostname us?" comparisons live in the Windows authentication path. Two disagreed in the Synacktiv research. The other two were not published. The next normalization function call is the next advisory.
CVE-2025-24054 names the class. Shell metadata file formats contain URL elements that the handler resolves at metadata-render time. The .URL and .library-ms formats are two members. The list of registered Shell handlers that read their own URL fields at render time is finite. It has not been published.
The next case file is in one of those four paragraphs.
The prediction
The next in-wild exploited Microsoft advisory in this pattern will have three traits. Its title will name one Windows component. Its research writeup will identify at least two components the title does not own. Its patch will land in the component the title names.
The substrate is one of three. CLFS, which has produced five in-wild use-after-free CVEs in 36 months and whose last patch shipped in April 2025. Nineteen months have passed. That is longer than any gap between the previous five. Or a Shell metadata URL leak, in a file format registered under a shell handler, whose URL element the handler resolves at render time. The .URL and .library-ms formats are two of this family. Or a Windows auth identity disagreement, in which two components call different Win32 string functions on the same hostname or principal name and get different answers. Synacktiv published two disagreements in one body of work. The others exist.
The most specific call: an ADCS-reachable Kerberos relay path whose advisory does not mention ADCS. The CVE-2026-26128 PoC's README names it as live on patched hosts, and Microsoft's March 2026 patch did not cover it. A later reader can mark this one called or missed against Microsoft's next SMB, Kerberos, or Certificate Services bulletin.
You decided what fit in the bulletin and what got a documentation edit. When the next advisory lands, I will quote it against this one.