# SMB Server Kerberos reflection via Ghost SPNs

Source: https://startwithidentity.com/cves/cve-2025-58726/
Last updated: 2026-08-29
License: content by Start with Identity. Cite the source URL.

---

## What broke

CVE-2025-58726 is the October 2025 SMB Server elevation of privilege that takes [CVE-2025-33073](https://startwithidentity.com/cves/cve-2025-33073/)'s Kerberos reflection and pairs it with Ghost SPNs created through DNS self-registration. Microsoft patched it in the October 2025 updates.

## Why it matters

DNS self-registration is on by default in most AD shops. That convenience is now part of an elevation chain. [KerberLoss](https://startwithidentity.com/cves/cve-2026-25177/) later showed another way to play with SPN uniqueness. SPNs are identity, not inventory trivia.

## What to do

- Patch Windows Server for October 2025.
- Disable insecure dynamic DNS updates where you can. Monitor new SPN writes on privileged computer accounts.
- Cross-check with [CVE-2026-25177](https://startwithidentity.com/cves/cve-2026-25177/) (invisible-Unicode SPN bypass) when you write the AD hardening ticket.

## After you patch

Active Directory compromise is not contained by patching, because the artifacts an attacker creates outlive the vulnerability.

- **Rotate the krbtgt account twice**, with the replication interval between rotations, if there is any indication of ticket forgery. One rotation is not enough.
- **Audit AD CS certificate templates** for enrolment and enrollee-supplied-subject permissions, which are the most common escalation path left behind. See [certificate lifecycle](https://startwithidentity.com/glossary/certificate-lifecycle/).
- **Review privileged group membership and delegation rights** (Domain Admins, DnsAdmins, constrained and resource-based constrained delegation) for changes during the window.
- **Hunt for tickets with anomalous lifetimes or encryption types**, and for authentications to services that identity never touches.
- **Treat any issued certificate as a durable credential**: revoking a user's password does not revoke a certificate that authenticates as them. See [privilege escalation](https://startwithidentity.com/glossary/privilege-escalation/) and [lateral movement](https://startwithidentity.com/glossary/lateral-movement/).

## Sources

- [NVD: CVE-2025-58726](https://nvd.nist.gov/vuln/detail/CVE-2025-58726)