Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-27912: ResetNightmare

Published Apr 14, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.0High · v3.1
EPSS0.59%49th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-27912CWE-863

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

3 exploits validated by Mallory's analysis.

View more in app →
ResetNightmareThis repository is a small, focused proof-of-concept for CVE-2026-27912 'ResetNightmare'. It contains one substantive code file, ResetNightmare.ps1, plus a README and license. The PowerShell function Invoke-ResetNightmare automates an Active Directory attack chain against an unpatched domain controller: it optionally creates a new user or computer object in a specified OU/container, grants the current operator GenericAll over that object, sets its password, enables it, changes its userPrincipalName to match the victim's sAMAccountName, requests a Kerberos TGT using Rubeus with principal type enterprise for the kadmin/changepw service, clears the fake UPN, and then uses the obtained ticket to reset the victim account's password. After success it deletes the temporary TGT file and restores the original UPN if one existed. The exploit targets both user and computer accounts and is operational rather than just demonstrative because it performs the full password-reset workflow and cleanup, but it relies on an external tool (Rubeus.exe) and a vulnerable AD environment. There are no hardcoded remote IPs or URLs; the main fingerprintable targets are AD/Kerberos identifiers, LDAP filters, the local Rubeus path, the temporary TGT file, and distinguished names/PSDrive roots used for directory manipulation.Semperis-Community · Disclosed Aug 2, 2026 · powershell · markdown · network · localPoCResetNightmare-impacketThis repository is a small standalone Python exploit tool for CVE-2026-27912 ('ResetNightmare'). It is not part of a larger exploit framework. The repository contains one substantive code file, resetnightmare.py, plus a README, requirements, license, and gitignore. The Python script is the clear entry point and implements the full attack workflow using impacket and ldap3. Core capability: the tool resets the password of a target Active Directory account by abusing enterprise principal name mapping during a Kerberos AS-REQ for the kadmin/changepw service. The operator authenticates to LDAP, identifies or creates a helper account ('UPNUser'), temporarily sets that account's userPrincipalName to the target account's sAMAccountName, requests a change-password TGT as an NT_ENTERPRISE principal, then uses kpasswd to set a new password on the target account. Afterward it clears/restores the helper account UPN. This is an active exploitation tool, not merely a detector. Repository structure and purpose: - README.md: documents the vulnerability, attack logic, prerequisites, usage examples, troubleshooting, and post-exploitation follow-up. - requirements.txt: declares impacket and ldap3 dependencies. - resetnightmare.py: main exploit implementation. Observed code structure from resetnightmare.py: - Argument parsing and CLI handling for operator credentials, target account, new password, helper account, Kerberos/NTLM auth modes, hashes/AES keys, LDAPS toggle, recon modes, and account creation path. - ADConnection class wrapping ldap3 operations for LDAP/LDAPS binds and directory actions. - Logic for reconnaissance (--find, --list-ous), including ACL/right evaluation to identify writable UPN targets and locations where new objects can be created. - Optional helper-account creation flow, including password setting and enablement, which requires LDAPS. - Kerberos TGT request logic via impacket getKerberosTGT using the service principal kadmin/changepw. - Password change execution via impacket.krb5.kpasswd.changePassword. - Cleanup/restoration logic to revert the fake UPN after exploitation. Network/target behavior: the exploit communicates directly with a domain controller over LDAP/LDAPS (389/636) and Kerberos password-change functionality. It accepts a DC hostname or IP and supports NTLM, pass-the-hash, or Kerberos LDAP bind modes. The README examples use 10.0.0.10 as the DC IP. The exploit targets AD user or computer accounts, including machine accounts ending in '$'. Overall assessment: this is an operational exploit/abuse tool for AD environments. It includes a real payload effect (credential reset), supports multiple authentication methods, performs prerequisite reconnaissance, and includes cleanup, making it more than a simple proof of concept.mihat2 · Disclosed Aug 8, 2026 · python · network · webPoCKerberos-CVE-2026-27912Repository contains a single substantial Python exploit script, resetnightmare.py, plus README, requirements, and license. The script is presented as an exploit for CVE-2026-27912, a Windows Kerberos/Active Directory elevation-of-privilege issue enabling unauthorized password reset. Based on the README and visible code structure, the exploit automates a multi-step AD attack chain: manipulate a controlled account's UPN, request a Kerberos TGT using an enterprise-style name, clear or restore the UPN, perform a password reset against the chosen target, and verify success. The code is not a framework module; it is a standalone operational tool with CLI argument parsing, configuration defaults, logging, retry logic, status/result dataclasses, optional rich-text UI, and support for cleanup/rollback. It relies on external Windows tooling, especially Rubeus.exe, and likely shells out to PowerShell/AD commands for directory operations. The main capability is account takeover of arbitrary user or computer accounts in a vulnerable AD domain by setting a new password. Fingerprintable artifacts are mostly local file/tool references and AD-specific identifiers rather than hardcoded network IOCs; the Domain Controller is operator-supplied at runtime. Overall, this is an exploit tool rather than a detector, with practical attack automation but no highly modular payload framework, making OPERATIONAL the best maturity assessment.oxstussz-eng · Disclosed Aug 14, 2026 · python · markdown · network · localPoC
Exposure surface

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.

VendorProductType
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

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.
Activity feed

Recent activity

30 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cyberveilleNews · Oct 7, 2026CVE-2026-27912 ResetNightmare : PoC de réinitialisation de mot de passe via Kerberos Change Password | CyberVeilleA validation flaw in the Kerberos Change Password protocol affecting unpatched Active Directory domain controllers. An attacker who can modify the userPrincipalName of an attacker-controlled account, or create an account with the necessary permissions, can manipulate Kerberos ticket issuance to reset a target user or computer account's password without knowing its existing password. The content describes a publicly available proof of concept, not observed in-the-wild exploitation.Read more ↗splunk researchNews · Sep 23, 2026Detection: Windows AD User Suspicious UPN Change | Splunk Security ContentAn Active Directory identity-spoofing vulnerability that allows an attacker with WriteProperty rights on their own userPrincipalName attribute to set it to another account's sAMAccountName. The KDC resolves an NT-ENTERPRISE Kerberos pre-authentication request against the spoofed UPN and issues a kadmin/changepw TGT that can be used to change the target account's password through kpasswd on port 464. The reference provides a detection for suspicious self-modification of the UPN using Windows Security Event 4738; it does not report observed exploitation.Read more ↗splunk researchNews · Sep 23, 2026Resetnightmare | Splunk Security ContentA vulnerability demonstrated through manual exploitation using a public exploit in a Splunk attack_range simulation. The content does not describe its technical mechanism, affected products, or real-world exploitation.Read more ↗semperis blogNews · Aug 5, 2026AD Research: Two new vulnerabilities could lead to full domain takeoverA severe Active Directory privilege escalation vulnerability in the Kerberos password change flow that lets an attacker with write access to a UPN set it to a target's SamAccountName, obtain a misleading NT-ENTERPRISE TGT, and reset the target account's password to achieve domain takeover.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity26Community discussion across Reddit, Mastodon, and other social sources.