Windows and Cloud DNS Abuse Research Enables DoS and Kerberos Relay Scenarios
Vulnerability Disclosure · 2 sources · Updated 5mo ago · First seen Jan 21, 2026

Multiple security research teams reported DNS-related abuse paths that can be weaponized for denial-of-service and authentication relay. Unit 42 described how Azure Private Endpoint/Private Link DNS behavior can be leveraged—accidentally or maliciously—to disrupt access to Azure resources by effectively “over-privatizing” name resolution, creating a DoS condition for services such as Storage Accounts, Key Vault, Cosmos DB, Azure Container Registry, Function Apps, and OpenAI accounts. Their assessment suggested the exposure is not rare in the wild (they observed 5%+ of Azure storage accounts in configurations susceptible to this DoS pattern) and noted Microsoft guidance around internet fallback as a partial mitigation, alongside recommendations to scan environments for susceptible configurations.
Separately, Cymulate detailed a Kerberos authentication relay technique via DNS CNAME abuse in Windows/Active Directory environments: an on-path attacker can influence DNS CNAME resolution so Windows clients request Kerberos service tickets for attacker-chosen SPNs, enabling relays to services like SMB/HTTP when signing or Channel Binding Tokens (CBT) are not enforced. Cymulate stated Microsoft acknowledged the behavior and responded by improving target-service resilience, including backported CBT support for HTTP.sys in supported Windows Server versions (released in a January patch cycle). A third report from Positive Technologies analyzed an RCE path in Windows Telephony Service (TAPI) via arbitrary file write from a low-privileged client, which is a distinct Windows local/service exploitation topic and not part of the DNS/Kerberos abuse story.


