Skip to main content
Mallory
HighVulnerability

CVE-2026-25177: KerberLoss

Published Mar 10, 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.8High · v3.1
EPSS1.4%72nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-25177CWE-641 · Improper Restriction of Names for…

KerberLoss is an authenticated privilege-escalation vulnerability in Microsoft Active Directory Domain Services caused by inconsistent handling of comparison-ignorable Unicode characters in service principal names (SPNs). Active Directory stores these characters verbatim but ignores certain characters during name comparisons, allowing specially crafted servicePrincipalName values to bypass SPN and SPN-alias uniqueness protections. An attacker with SPN write permissions on a user or computer account can introduce conflicting SPNs, manipulate service-account resolution, disrupt Kerberos authentication, and support SPN-jacking in constrained-delegation scenarios.

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.

Exploitation can disrupt HOST-mapped services by causing service tickets to be encrypted with the wrong account key, resulting in KRB_AP_ERR_MODIFIED. Duplicate explicit SPNs can also cause KDC_ERR_S_PRINCIPAL_UNKNOWN, denying Kerberos authentication and potentially forcing clients to fall back to NTLM where permitted. In suitable constrained-delegation configurations, SPN-jacking can enable privilege escalation, potentially reaching SYSTEM-level privileges. These outcomes depend on the targeted SPNs, account permissions, delegation configuration, and authentication fallback policy.

Mitigation

If you can’t patch tonight, do this now.

Restrict SPN WriteProperty permissions on user and computer objects to accounts that require them, reviewing delegated permissions that permit arbitrary SPN changes. Disable NTLM where operationally feasible to prevent Kerberos failures from triggering authentication downgrade; this does not prevent SPN collisions or denial of service. Enable successful Audit Directory Service Changes auditing and appropriate WriteProperty audit SACLs, then monitor domain controller Security Event 5136 for servicePrincipalName changes containing invisible Unicode characters and unexpected modifications by non-machine accounts.

Remediation

Patch, then assume compromise.

Install the Microsoft security updates released on March 10, 2026, that address CVE-2026-25177, or superseding updates, on all affected Active Directory domain controllers. Review servicePrincipalName attributes for unauthorized values containing invisible Unicode characters and remove confirmed malicious entries while preserving legitimate SPNs.

Public exploits

Exploits

No validated public exploits yet. Hidden: 3 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
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 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
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-25177 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2026-25177 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-25177?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2026-25177.
Is there a patch for CVE-2026-25177?
Install the Microsoft security updates released on March 10, 2026, that address CVE-2026-25177, or superseding updates, on all affected Active Directory domain controllers. Review servicePrincipalName attributes for unauthorized values containing invisible Unicode characters and remove confirmed malicious entries while preserving legitimate SPNs.
What products are affected by CVE-2026-25177?
Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, Microsoft Corporation Windows 11 23h2, and 11 more.
How severe is CVE-2026-25177?
CVE-2026-25177 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 1.4% (72nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

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

View more in app →
metasploit pull requestsNews · Oct 10, 2026Add KerberLoss (CVE-2026-25177) Active Directory SPN confusion auxiliary module by adilalperenciftci · Pull Request #22005 · rapid7/metasploit-frameworkAn Active Directory service principal name (SPN) comparison inconsistency. An operator with unrestricted WriteProperty permission on a target account's SPN attribute can insert a value containing comparison-ignorable Unicode characters, such as U+200C. Clean SPN lookups can then resolve to that account or collide with existing SPNs, potentially producing KDC_ERR_S_PRINCIPAL_UNKNOWN. The described Metasploit module demonstrates LDAP resolution changes in an isolated Windows Server 2019 domain controller environment; the content cautions that LDAP resolution alone is not cryptographic proof of service-ticket hijacking.Read more ↗splunk researchNews · Sep 28, 2026Kerberloss | Splunk Security ContentKerberLoss is the named vulnerability represented in an attack-simulation dataset involving a user account modifying computer-object service principal names (SPNs) and injecting invisible Unicode characters into their values. The dataset contains Windows Security Event 5136 logs. The content does not explain the vulnerability's underlying cause, affected product versions, or security impact, and does not establish real-world exploitation.Read more ↗splunk researchNews · Sep 25, 2026Detection: Windows AD Computer SPN Modified By User Account | Splunk Security ContentReferenced as relevant to detecting anomalous Active Directory computer SPN modifications by user accounts with delegated WriteProperty rights. The content does not describe the vulnerability's underlying mechanism, affected versions, or confirmed exploitation.Read more ↗splunk researchNews · Sep 25, 2026Detection: Windows AD SPN Unicode Collision Injection | Splunk Security ContentAn Active Directory SPN-handling vulnerability caused by inconsistent Unicode normalization between LDAP uniqueness checking and the Kerberos KDC. An attacker with write access to a machine account's servicePrincipalName attribute can introduce an invisible-Unicode collision SPN, causing Kerberos authentication failures and denial of service or forcing clients to fall back to NTLM. The reference provides a detection using Windows Security Event 5136 to identify SPN additions or modifications containing invisible Unicode characters; it does not establish real-world exploitation or patch availability.Read more ↗
+2 more in the timeline. Sign up to see them
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 activity18Community discussion across Reddit, Mastodon, and other social sources.