TL;DR: Semperis argues that invisible Unicode can create lookalike identities and bypass name checks in Active Directory. That can turn directory changes into authentication failures or domain-wide compromise when SPN and UPN writes are not tightly controlled.
Editorial analysis by NHI Mgmt Group, based on content published by Semperis: “Identity Crisis: Novel Vulnerabilities Leading to Kerberos Downgrade, DoS, and Full Domain Takeover”.
Key questions
Q: Why do conflicting SPNs create such a serious Kerberos risk?
A: A conflicting SPN changes which account Kerberos treats as the owner of a service.
Q: How can security teams tell if Unicode abuse is hiding in Active Directory?
A: Look for duplicate-looking objects, unexpected hidden characters in attribute values, and SPN or UPN changes that do not match normal delegation or onboarding patterns.
Q: What breaks when hidden Unicode is allowed in Active Directory object names?
A: It breaks the assumption that displayed names and directory-resolved identities are the same thing.
Practitioner guidance
- Harden attribute write permissions Restrict who can modify SPN, UPN, and other lookup-sensitive attributes on user and computer objects, especially where generic write rights exist on delegated OU structures.
- Audit for invisible character abuse Scan Active Directory objects for hidden Unicode characters, duplicate-looking names, and conflicting SPN or UPN values that could alter directory resolution.
- Monitor directory modifications at the DC Enable SACLs and review Security event ID 5136 for SPN and UPN changes that collide with existing identities or introduce non-default naming patterns.
Bottom line: Invisible Unicode handling in Active Directory creates a genuine identity integrity problem because controllers, operators, and LDAP filters can disagree on what a name means.
Glossary terms: Identity Comparison, ServicePrincipalName, User Principal Name, Unicode Normalization
What's in the full report
Semperis's full analysis covers the exploit mechanics this post intentionally leaves at a higher level:
- Step-by-step reproduction of the KerberLoss SPN collision path and its effect on Kerberos ticketing
- Step-by-step reproduction of the ResetNightmare UPN abuse path and how it leads to Domain Admin
- Detection examples using Security event ID 5136 and the Semperis DSP indicators named in the article
- Disclosure timeline and patch dates for CVE-2026-25177 and CVE-2026-27912
👉 Read Semperis's analysis of Unicode identity confusion in Active Directory →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Directory identity is only as strong as the comparison rules behind it: If a controller and an administrator do not evaluate names the same way, then uniqueness checks become a cosmetic control rather than a security control. Active Directory’s Unicode edge cases show that identity integrity can fail even when permissions look intact. The implication is that directory governance must include parser behaviour, not only access policy.
A question worth separating out:
Q: Should organisations rely on visual review to catch directory identity abuse?
A: No. Visual review is useful for triage, but it is not enough when the directory can store values that render ambiguously or are ignored by different components. Organisations need attribute-level validation, least-privilege write access, and audit telemetry because the attack succeeds through directory semantics, not just through user deception.
👉 Read our full editorial: Unicode identity confusion in Active Directory enables Domain Admin