CVE-2026-27912: ResetNightmare
- Vendor
- Microsoft Corporation
ResetNightmare is an improper authorization vulnerability in Windows Kerberos affecting unpatched Active Directory domain controllers. An authenticated attacker with permission to modify an attacker-controlled user or computer object's userPrincipalName can set that attribute to a target account's sAMAccountName and request a Kerberos change-password ticket using the NT-ENTERPRISE name type. The resulting ticket carries the target's name but the requester's SID. After changing or clearing the manipulated UPN, the attacker can use the ticket through the Kerberos Change Password protocol to reset the target account's password without knowing its existing password. This exchange bypasses the PAC_REQUESTOR_SID validation normally performed during a ticket-granting service exchange, enabling privilege escalation and potentially complete domain compromise.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An attacker can reset a target user or computer account's password without knowing the current password, subject to the target's minimum password age policy. Resetting a privileged account allows authentication as that account and can result in Domain Admin access and complete domain takeover. Password replacement can also disrupt legitimate account access and services dependent on the affected credentials.
Mitigation
If you can’t patch tonight, do this now.
Enforce least privilege on userPrincipalName modification rights and delegated user or computer object creation permissions. Audit domain controller directory changes, including Security Event 5136 for suspicious UPN modifications. Enable User Account Management auditing and monitor Event 4738 for account self-modifications that set a UPN without an @ sign, especially values matching another account's sAMAccountName. Investigate these changes in context because provisioning and migration workflows can generate similar events. Monitoring supports detection rather than correcting the authorization flaw; no separate vendor workaround is identified.
Remediation
Patch, then assume compromise.
Apply the Microsoft security updates released on April 14, 2026 that address CVE-2026-27912 to all affected Active Directory domain controllers. Select the applicable updates for each Windows Server version through the Microsoft Security Update Guide or associated KB documentation.
Exploits
3 exploits validated by Mallory's analysis.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-27912 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2026-27912 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-27912?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-27912, the earliest disclosed Aug 2, 2026.
- Is there a patch for CVE-2026-27912?
- Apply the Microsoft security updates released on April 14, 2026 that address CVE-2026-27912 to all affected Active Directory domain controllers. Select the applicable updates for each Windows Server version through the Microsoft Security Update Guide or associated KB documentation.
- What products are affected by CVE-2026-27912?
- Microsoft Corporation Windows Server 2012, Microsoft Corporation Windows Server 2012 R2, Microsoft Corporation Windows Server 2016, Microsoft Corporation Windows Server 2019, Microsoft Corporation Windows Server 2022, and 3 more.
- How severe is CVE-2026-27912?
- CVE-2026-27912 has a CVSS v3.1 score of 8.0 (High) and an EPSS score of 0.59% (49th percentile) as of Oct 16, 2026.
Recent activity
30 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.