Summary

Within days of Microsoft’s record July Patch Tuesday, a researcher publicly released a proof-of-concept exploit for a new Windows zero-day vulnerability in the User Profile Service, dubbed LegacyHive. The flaw enables an arbitrary registry hive load, leading to local privilege escalation, and works across all currently supported Windows desktop and server versions — including those fully patched with the July 2026 updates.

The vulnerability was not included in July’s Patch Tuesday, meaning it remains unpatched. The researcher chose full disclosure after Microsoft’s standard coordinated disclosure process, citing the exploitability and the compressed timeline between vulnerability discovery and weaponization that AI tools now enable. The PoC code is publicly available on GitHub.

LegacyHive joins a growing list of Windows privilege escalation primitives in active circulation. Because it targets the User Profile Service — a component present in virtually every Windows installation — the attack surface is extremely broad. Local privilege escalation vulnerabilities are a critical step in post-exploitation chains, allowing attackers to move from user-level access to SYSTEM.

Sources

Commentary

This is the post-Patch Tuesday drop that defenders dread: a working PoC for a new LPE, unpatched, targeting the entire Windows install base. The User Profile Service is not an exotic component — it’s load-bearing infrastructure that every Windows system touches at login. Arbitrary hive loads are a well-understood privilege escalation primitive with a long history in Windows exploitation, and having a working PoC in the wild immediately elevates this to high operational priority for red teams and defenders alike.

The timing is notable: researchers are increasingly dropping PoCs faster because the window of “responsible disclosure grace period” is collapsing. When AI can generate weaponized exploits from patch diffs in hours, holding a PoC for 90 days only benefits attackers who independently find it. The coordinated disclosure model is under strain and this is another data point in that conversation.

By Allan