On this page (6 sections)

CVE-2026-85844 is a critical authentication bypass in Windows Kerberos. According to the NVD record, an unauthorized attacker can use an alternate path or channel to elevate privileges over a network. The entry was published on 2026-11-10 with a CVSS score of 9.8.

If you run Windows servers, domain controllers or any service that relies on Kerberos for sign-in, this is one to track today. The public record is short, so this article separates what is confirmed from what still has to be checked against Microsoft's own guidance.

What is confirmed so far

The only primary source is the NVD entry, which repeats the short description above and points to the Microsoft Security Response Center (MSRC) update guide entry as its reference. The record gives the CVSS base score of 9.8, a critical rating, and the weakness type CWE-288.

Coverage is thin so far: only one independent publisher has reported on the story. The available material does not list affected builds, fixed builds, an attack complexity breakdown, or any report of exploitation in the wild. Treat any claim beyond the description as unconfirmed until Microsoft's advisory says otherwise.

What the weakness class means

CWE-288 describes a system that protects its main login path but leaves another route to the same function that skips the check. Think of a building with a guarded front door and an unlocked side entrance. The attacker does not break the lock; they simply never go through it.

Kerberos is the ticket-based protocol Windows domains use to prove who a user or service is. A bypass in this area is serious because other systems trust the identity Kerberos vouches for. The record says the result is privilege elevation, so an attacker without valid authorization could end up acting with higher rights than they should have. The exact mechanism and the required conditions are not described in the research, and this article does not speculate about them.

Who is realistically exposed

The description says the attack works over a network, so reachability matters. The systems most likely to matter are those that take part in Kerberos authentication:

  • Domain controllers and other Active Directory infrastructure
  • Windows file, application and database servers joined to a domain
  • Web applications and intranet sites using Windows integrated authentication
  • Hosting and agency environments that run Windows servers for clients

Which Windows versions and roles are actually vulnerable has not been confirmed in the research. Do not assume you are safe because a server is not a domain controller until the advisory states the affected scope.

How to check your exposure

Start by finding out what you run and whether the update is available for it. Open the MSRC entry for CVE-2026-85844 and compare the listed products and builds with your inventory.

On a Windows server, this PowerShell command lists the 20 most recently installed updates with their install dates. Run it in an elevated PowerShell window and look for the update number named in the Microsoft advisory once you have it:

List installed Windows updates, newest first (run in PowerShell on the server)PowerShell
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 20 HotFixID, Description, InstalledOn

This read-only command shows the Windows edition and build so you can match it against the advisory's affected list:

Show Windows edition and build number (run in PowerShell)PowerShell
Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber

What to do now

  1. Open the Microsoft advisory for CVE-2026-85844 and note the affected products and the fixing update.
  2. List every domain controller and Kerberos-dependent server, and rank them by exposure, with domain controllers first.
  3. Test the update on a non-production system, then deploy it to domain controllers and critical servers as soon as testing allows.
  4. Restrict network access to Kerberos and domain services so only the networks that need them can reach them.
  5. Review recent sign-in and privilege-change events on domain controllers for anything unexpected, and keep the logs.
  6. Confirm that your patch tooling reports the update as installed, and record any systems that cannot be patched yet.
  7. Re-check the advisory and the NVD entry for updates on exploitation status or mitigations.
Caution. Installing updates on domain controllers can require a restart. Schedule it, keep at least one healthy domain controller available during the work, and test first so authentication for your users and services is not interrupted.

If the advisory lists a workaround, apply it only as a stopgap. A workaround is not a replacement for the update.

Detection and monitoring afterwards

Because exploitation is not confirmed, focus on signals that would matter for any authentication bypass: unexpected privileged accounts or group membership changes, sign-ins from unusual hosts, and new services or scheduled tasks on servers that rarely change. Make sure domain controller logs are collected centrally and retained long enough to look back.

For internet-facing sites that depend on Windows authentication, watch for unexpected changes in certificates, DNS records and response headers, since those can signal that something upstream has changed. Webforta Monitor tracks certificate, DNS and header changes, and the free SSL checker can confirm your certificates are valid. These are general hygiene checks and do not detect or fix this vulnerability.

If you suspect a system was compromised before patching, follow the steps in Website hacked: what to do and treat any account that could have been elevated as exposed. For a broader baseline, see the small business website security guide.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-85844: Authentication bypass using an alternate path or channel in Windows Kerberos allows an unauthorized attacker to elevate privileges over a network.nvd.nist.gov ·
  • Windows
  • Kerberos
  • CVE-2026-85844
  • Authentication bypass
  • Active Directory