LegacyHive: a public Windows technique that redirects a profile's Local AppData into the NT Object Manager namespace via offline hive edits, reproduced on fully patched systems
LevelBlue reproduces Nightmare Eclipse's latest Windows PoC on a July-2026-patched build, no CVE, no fix, and the abuse uses only legitimate APIs
Analysis
LevelBlue is explicit that LegacyHive is not a traditional vulnerability, like the rest of the Nightmare Eclipse series it explores a corner of Windows rather than introducing a bug, in this case profile initialisation and registry hive loading (LevelBlue SpiderLabs, 2026-07-27). The chain runs in seven steps and every one uses documented, legitimate machinery. It first creates a directory hierarchy inside the NT Object Manager namespace via NtCreateDirectoryObjectEx called from user mode, which LevelBlue notes is itself unusual because normal applications almost never create Object Manager namespaces after system initialisation, then builds native Object Manager symbolic links inside it with NtCreateSymbolicLinkObject (not Windows shortcuts or NTFS junctions) to form the redirection layer (LevelBlue SpiderLabs, 2026-07-27). It then opens a helper account's ntuser.dat directly and edits it offline through Microsoft's Registry Offline API, replacing the Local AppData value under Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders with the redirected namespace path, before saving the hive back over the original (LevelBlue SpiderLabs, 2026-07-27).
The timing step is what makes it reliable rather than racy. Instead of retrying until it wins, the exploit takes a batch opportunistic lock on UsrClass.dat, which pauses execution until profile initialisation reaches the expected point; LevelBlue's framing is that the exploit does not fight the Windows startup process but uses Windows' own synchronisation features to control it (LevelBlue SpiderLabs, 2026-07-27). It then launches a process as the helper user via CreateProcessWithLogonW with LOGON_WITH_PROFILE (the point being not execution but forcing a normal profile load that consumes the tampered hive) and validates success through RegOpenUserClassesRoot. Cleanup removes temporary files but leaves the modified registry configuration and namespace redirection in place, so the persistence lives in on-disk state rather than in a process or scheduled task (LevelBlue SpiderLabs, 2026-07-27).
Two facts bound how much this should worry a defender, in opposite directions. Downward: the released proof-of-concept requires the attacker to control a low-privileged account and hold valid credentials for a separate helper account on the same machine, which LevelBlue says makes it more useful as a post-compromise capability than a standalone attack, and notes those limitations were intentionally introduced before publication to discourage immediate abuse (LevelBlue SpiderLabs, 2026-07-27). This is not remote, not pre-authentication, and not privilege escalation from nothing. Upward: what the attacker does not need is the credentials of the account whose profile data they end up reaching (that is the whole point of the technique) and LevelBlue's teams reproduced the complete chain on fully patched Windows with July 2026 updates installed, with no Microsoft mitigation existing for this class of abuse (LevelBlue SpiderLabs, 2026-07-27). LevelBlue also cautions that the published code demonstrates the technique rather than exhausting it, and expects variants to change how profile loading is triggered or which hives are targeted while relying on the same building blocks.
Triage: every individual operation here is legitimate (offline hive editing, an oplock on a profile hive, a logon-with-profile process launch) and LevelBlue's explicit position is that each is legitimate in isolation while observing them together in a short window is highly unusual and well suited to behavioural correlation. Note specifically that the target executable carries no discriminating value: LevelBlue demonstrates the PoC's notepad.exe is trivially substitutable, so detection must anchor on the calling pattern (a cross-account CreateProcessWithLogonW using LOGON_WITH_PROFILE, routed through the seclogon service) rather than on any process name.
Cited evidence
As released, it requires control of a low-privileged account and the credentials of a separate helper account, making it more useful as a post-compromise capability than as a standalone attack. According to the disclosure, these limitations were intentionally introduced before publication to discourage immediate abuse.
the registry modification itself is legitimate. LegacyHive uses valid registry structures, valid APIs, and a valid registry value type. The abuse happens because Local AppData no longer points to the user's normal profile directory. Instead, it points into the attacker-controlled Object Manager namespace.
For EDR platforms with visibility into native Windows APIs, the strongest signals are user-mode invocations of NtCreateDirectoryObjectEx and NtCreateSymbolicLinkObject. These functions are rarely used outside system components, debugging tools, or specialized research utilities. Seeing both from the same process should immediately warrant investigation.
LevelBlue OpsIntel CTI and Threat Operations and Research (THOR) teams reviewed and reproduced the complete LegacyHive exploitation chain on fully patched Windows systems with the July 2026 Patch Tuesday updates installed, confirming the PoC functions as described.
Improper link resolution before file access ('link following') in Windows User Profile Service allows an authorized attacker to elevate privileges locally.
the advisory is a solid match for Nightmare Eclipse’s description of LegacyHive
Updates1
The entry on LegacyHive (the Nightmare Eclipse Windows proof-of-concept that LevelBlue reproduced on a fully patched July-2026 build) recorded that the vendor offered no mitigation for that class of abuse. Microsoft's August Patch Tuesday appears to have closed it. CVE-2026-62832 is described in Microsoft's own record as "Improper link resolution before file access ('link following') in Windows User Profile Service allows an authorized attacker to elevate privileges locally", scored CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), rated Important, recorded as publicly disclosed before the fix, not exploited, and assessed as "Exploitation More Likely" (MSRC, 2026-08-11).
Microsoft does not name LegacyHive, and the identification is worth attributing precisely rather than assuming. Rapid7 states that between the public disclosure and the advisory FAQ (which describes an authenticated attacker who has credentials for another account and loads another user's registry hive) "the advisory is a solid match for Nightmare Eclipse's description of LegacyHive" (Rapid7, 2026-08-11). That is an assessment by a third party, not a vendor mapping, which is why this entry carries it as such.
The independent detail that makes the match credible comes from the unofficial patch that preceded the official one. 0patch analysed the flaw in July and describes it in the same terms: the vulnerability lies in the Windows User Profile Service, where a time-of-check-to-time-of-use condition lets a local attacker use a symbolic link to confuse the service into loading any user's registry hive instead of the requesting user's, ending up mounted in the attacker's own registry space with read/write permissions. Its root cause, per 0patch, is an access-check fallback: when the service can open the hive file with full access it mounts it under the requesting user's identity using NtLoadKey3, which supports impersonation, but when it cannot, it falls back to the older NtLoadKeyEx without impersonation, so the hive loads with full access as Local System. The consequence 0patch names is the same one the original entry described from the attacker's side: read the target user's stored secrets, or replace paths to trusted executables and DLLs so they run the next time that user logs in (0patch, 2026-07-20).
For anyone who acted on the July coverage, the practical delta is short. The prerequisite is unchanged and still limits the blast radius; the attacker needs a local session plus credentials for a separate account, so this is a post-compromise escalation step rather than an entry point. The August cumulative update supersedes the 0patch micropatch as the remediation, and estates that deployed the community patch were covered in the interval. No action item ships with this entry: the fix arrives inside the ordinary Patch Tuesday cycle, and the entry exists to correct the record on the earlier "no fix available" framing rather than to open new work.
Sources4
Revision history
- Published 2026-07-29T0408Z-intel
- Update 2026-08-12T0411Z-intel
The LegacyHive proof-of-concept covered here on 2026-07-29, reproduced on fully patched Windows and described at the time as having no Microsoft mitigation, appears to be fixed. Microsoft's August Patch Tuesday shipped CVE-2026-62832, an improper-link-resolution elevation-of-privilege flaw in the Windows User Profile Service rated CVSS 7.8, publicly disclosed before the patch and assessed "Exploitation More Likely". Rapid7 assesses the advisory is a solid match for the researcher's description of LegacyHive; Microsoft's record does not name the technique, so the identification is Rapid7's judgement rather than a vendor confirmation.
Changed: cves evidence regions sectors sources tags techniques body
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.