Skip to main content
Mallory
← Back to News
identity-authentication-vulnerabilityendpoint-software-vulnerabilitywidely-deployed-product-advisorylateral-movement-method

Windows Active Directory Relay Attacks via SMB NTLM Reflection and Kerberos DNS CNAME Abuse

Vulnerability Disclosure · 3 sources · Updated 5mo ago · First seen Jan 19, 2026

Windows Active Directory Relay Attacks via SMB NTLM Reflection and Kerberos DNS CNAME Abuse

Two separate Windows authentication weaknesses were highlighted as enabling high-impact Active Directory compromise via relay-style attacks. One issue, CVE-2025-33073, affects Windows SMB client authentication and enables NTLM reflection: attackers can coerce lsass.exe (running as SYSTEM) to authenticate to attacker-controlled infrastructure using techniques such as PetitPotam, DFSCoerce, and Printerbug, then relay/reflect that authentication to gain SYSTEM-level access and potentially full domain compromise. Reporting emphasized that despite a June 2025 patch, the condition remains widely present in enterprise environments due to incomplete patch adoption, and exploitation can be enabled with relatively low prerequisites such as the ability to register a malicious AD DNS record (often permitted to Authenticated Users by default) or to perform local DNS poisoning.

A second technique described a Kerberos relay vector that abuses how Windows clients process DNS CNAME responses when building the SPN for TGS requests, allowing an on-path attacker (e.g., via ARP poisoning or DHCPv6/mitm6) to redirect victims to attacker-controlled services and obtain service tickets usable for relays and lateral movement. The write-up claims default configurations across Windows 10/11 and Windows Server 2022/2025 are susceptible, with potential impact including cross-protocol relays (e.g., HTTP→SMB/LDAP) and paths to RCE in some environments (e.g., via ADCS web enrollment scenarios). A separate Metasploit weekly wrap-up noted new and updated offensive modules (including AD privilege-escalation content), but it did not specifically tie to either of the two relay issues above.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

6 events · Jun 1, 2025 – Jun 30, 2026
  1. Jun 30, 20265mo ago

    Researchers release PoC for NTLM reflection bypass CVE-2026-24294

    A public proof-of-concept was released for CVE-2026-24294, an NTLM reflection bypass flaw affecting Windows Server 2025 that can yield SYSTEM-level access by relaying coerced NTLM authentication via SMB on a non-standard TCP port. The issue was described as bypassing Microsoft's earlier mitigation for CVE-2025-33073 and was demonstrated with modified coercion tooling and Impacket-based relay techniques.

    PoC Released for NTLM Reflection Bypass Flaw that Enables SYSTEM Access on Windows Server
  2. Jan 19, 202610mo ago

    Researchers detail ongoing exposure from unpatched SMB flaw

    A public write-up described how many enterprises remained unpatched months after the June 2025 fix for CVE-2025-33073, leaving systems exposed to NTLM reflection, coercion, and cross-protocol relay attacks affecting services such as LDAPS, ADCS, MSSQL, and WinRM.

  3. Jan 19, 202610mo ago

    Researchers publish Kerberos DNS CNAME relay PoC

    Researchers disclosed technical details for a Kerberos relay attack that abuses malicious DNS CNAME responses during TGS requests, and released a modified mitm6 proof-of-concept with CNAME poisoning support. The attack was reported to work against default Windows 10, Windows 11, Windows Server 2022, and Windows Server 2025 configurations when anti-relay controls are absent.

  4. Jan 1, 202611mo ago

    Microsoft releases January patch for Kerberos relay issue

    Microsoft shipped January 2026 patches for CVE-2026-20929, adding Channel Binding Token support for HTTP.sys to mitigate part of the Kerberos relay attack chain. The underlying DNS CNAME coercion behavior was reported to remain for other protocols.

  5. Oct 1, 20251y ago

    Microsoft notified of Kerberos DNS CNAME relay issue

    Researchers reported a Windows Kerberos weakness involving DNS CNAME-based service principal name manipulation to Microsoft. The disclosure reportedly occurred in October 2025.

  6. Jun 1, 20251y ago

    Microsoft ships patch for SMB client NTLM relay flaw

    Microsoft released June 2025 Windows updates for CVE-2025-33073, an SMB client vulnerability enabling NTLM reflection and relay attacks that can lead to privilege escalation and potential Active Directory compromise.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

6 linked
Windows 11Windows 10Windows Server 2025Windows Server 2022Active DirectoryWindows Kerberos

Organizations

1 linked
Microsoft Corporation
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.