A security researcher known as "Nightmare Eclipse" has publicly released a proof-of-concept (PoC) exploit for a new zero-day vulnerability in Microsoft Windows, dubbed "LegacyHive." The exploit enables a local attacker to achieve privilege escalation on fully updated Windows systems, including those with the July 2026 Patch Tuesday updates. The vulnerability exists within the Windows User Profile Service and allows a low-privilege user to access sensitive data from other user accounts on the same machine. Microsoft has not yet assigned a CVE identifier or released a patch for this flaw.
The LegacyHive exploit targets a logical flaw in how the Windows User Profile Service handles user registry hives. Specifically, it allows a malicious actor to mount a target user's UsrClass.dat hive file with read access. The UsrClass.dat file is a registry hive located in each user's profile (%USERPROFILE%\AppData\Local\Microsoft\Windows\UsrClass.dat) that stores per-user application settings and other data.
By mounting this hive, an attacker can read a wide range of application-specific information, Windows Explorer history, and other forensic artifacts. While the current PoC focuses on data access, the researcher suggests the technique could be modified to target more sensitive hives, potentially leading to the exposure of password hashes or other credentials. This disclosure is the latest in a series from the same researcher, who has previously released other Windows zero-days.
A functional proof-of-concept exploit has been made public. While this does not confirm in-the-wild attacks, the public availability of the exploit code significantly increases the likelihood of its adoption by threat actors. The attack requires an initial foothold on a system as a low-privilege user.
The immediate impact of the LegacyHive exploit is local privilege escalation (LPE) and information disclosure. An attacker with standard user access could use this exploit to read sensitive data belonging to other users, including administrators, on the same system. This data could facilitate further lateral movement, credential theft, or be exfiltrated for intelligence gathering. In a multi-user environment, such as a terminal server or shared workstation, the risk is significantly higher.
The following patterns may help identify attempts to exploit LegacyHive:
reg loadreg load command being used by non-administrative users or to mount hive files from other user profiles.\AppData\Local\Microsoft\Windows\UsrClass.datUsrClass.dat files outside of the currently logged-on user's profile directory.4656Key can be audited to track access to registry hives.userinit.exeuserinit.exe or other user session processes could indicate post-exploitation activity.reg load) from a user profile directory that does not belong to the process's owner.As of this report, there is no patch available from Microsoft for the LegacyHive vulnerability.
Organizations should focus on compensating controls and detection until a patch is released:
Unofficial micropatches released by 0Patch for 'LegacyHive' Windows zero-day, clarifying exploit allows SYSTEM privilege escalation via registry manipulation.
Using an EDR with strong behavioral detection rules is the most effective way to spot exploitation of this unpatched vulnerability.
Limiting the number of administrative accounts and restricting interactive logins can reduce the impact of a successful privilege escalation.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.