CVE-2026-27912: CVE-2026-27912: Improper authorization in Windows Kerberos allows an authorized attacker to elevate privil…
microsoft · windows server 2012 · NVD published 2026-04-14 · posted 2026-08-02 · last modified 2026-06-17
What it is
Improper authorization in Windows Kerberos allows an authorized attacker to elevate privileges over an adjacent network.
| Weakness | CWE-285 |
|---|---|
| CVSS vector | CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (source: [email protected]) |
| ATT&CK tactics | n/a |
Exploitation evidence
First exploit evidence seen: 2026-08-02 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
GitHub proof-of-concept repositories
3 public repositories from 3 accounts, first seen 2026-08-02. Most starred: Semperis-Community/ResetNightmare (223 stars), view repository.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: nomi-sec/PoC-in-GitHub.
How to fix it
Fixed versions
- microsoft windows server 2016: upgrade to 10.0.14393.9060 or later
- microsoft windows server 2019: upgrade to 10.0.17763.8644 or later
- microsoft windows server 2022: upgrade to 10.0.20348.5020 or later
- microsoft windows server 2022 23h2: upgrade to 10.0.25398.2274 or later
- microsoft windows server 2025: upgrade to 10.0.26100.32690 or later
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-27912 (Vendor Advisory)
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.