Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege network access to DNS server
-
DeliverySend crafted DNS protocol request
-
ExploitTrigger release of invalid pointer (CWE-763)
-
ExecutionCorrupt memory and hijack control flow
-
ImpactExecute arbitrary code on server
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Pointer release safety
|
| Exploitation Conditions | Exploitation requires the Windows DNS Server role to be installed and running, and the attacker must be an authorized/low-privileged principal able to reach the DNS service over the network (CVSS PR:L), per Microsoft's 'authorized attacker' wording. No user interaction is required (UI:N) and attack complexity is low (AC:L). Limiting factors: the target must actually host the DNS Server role (not a default workstation configuration), and the attacker must first hold at least low-level authentication/privileges rather than being fully anonymous - this narrows exploitation to insiders or attackers who have already gained a foothold or valid low-privilege credentials. |
| Impact | This is a genuine high-priority vulnerability for organizations running the Windows DNS Server role, though not an emergency-grade drop-everything issue at the time of analysis. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) describes network-reachable, low-complexity code execution with full confidentiality, integrity, and availability impact, requiring only low-level privileges (PR:L) and no user interaction. CISA's SSVC framework corroborates the severity on impact (Technical Impact: total) but tempers the urgency: Exploitation is rated 'none' (no observed or public exploitation) and Automatable is 'no', indicating it is not currently wormable or mass-exploitable. The CVE is NOT listed in CISA KEV and no public proof-of-concept is indicated in the provided data, so this reflects no public exploit identified at time of analysis. No EPSS score was supplied, so exploitation probability cannot be quantified from this data. The signals are therefore consistent rather than conflicting: high potential impact and network reachability, but no evidence of active or automatable exploitation yet. One data-quality note: the input Tag 'Information Disclosure' conflicts with the description, which states code execution and carries full I:H/A:H impact - this is an RCE-class flaw, not merely information disclosure, so the tag appears mislabeled. |
| Exploit ScenarioDerived | An attacker with low-privilege authenticated access reachable to a Windows DNS Server sends specially crafted DNS protocol traffic that triggers release of an invalid pointer or reference (CWE-763), corrupting memory on the server. By controlling the freed/invalid reference, the attacker achieves arbitrary code execution in the context of the DNS service over the network. No public exploit or proof-of-concept is identified at time of analysis, and no user interaction is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Memory corruption in the Windows DNS Server role allows an authorized, low-privileged attacker who can reach the DNS service over the network to execute arbitrary code in the context of the DNS service. The flaw is a release of an invalid pointer or reference (CWE-763) rated CVSS 8.8 with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, meaning no user interaction, low attack complexity, net-unauthenticated reachability but a low-privilege prerequisite (PR:L) matching Microsoft's 'authorized attacker' wording. Exposure is limited to hosts that actually run the DNS Server role - Windows Server 2012 through 2025 (including Server Core installations) and Windows 10/11 builds with the role enabled - and at the time of analysis there is no public exploit code identified and CISA's SSVC assessment records exploitation as 'none', so this is a high-priority hardening item for DNS-hosting infrastructure rather than an emergency drop-everything event. Vendor patches are available, and the underlying build-level fixes are enumerated in the affected-version data below.
RemediationAI
Apply the vendor patch: Microsoft has released fixes for this issue and the patch is available from the vendor via the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83889) - install the current cumulative update for each affected build so the OS reaches at least the fixed levels, e.g. 6.2.9200.26434 (Server 2012), 6.3.9600.23470 (Server 2012 R2), 10.0.14393.9612 (Server 2016 / Win10 1607), 10.0.17763.9376 (Server 2019 / Win10 1809), 10.0.19044.7807 (Win10 21H2/22H2), 10.0.20348.5761 (Server 2022), 10.0.22631.7652 (Win11 23H2), 10.0.26100.33650 (Server 2025), 10.0.26100.9711 (Win11 24H2), 10.0.26200.9711 (Win11 25H2), 10.0.28000.3231 (Win11 26H1) and 10.0.26300.9711 (Win11 26H2); note that Server 2012 and 2012 R2 are out of mainstream support, so confirm extended-support (ESU) entitlement before relying on those builds. Because exploitation requires an authenticated, low-privileged principal who can reach the DNS service, the most effective compensating controls while patching are: firewall the DNS Server role so only trusted resolver clients, secondary/forwarder servers and management hosts can reach TCP/UDP 53 and the DNS RPC/management endpoints (this blocks external and cross-segment attackers but requires accurate inventory of legitimate resolvers and can break split-horizon or roaming-client scenarios); remove or tightly scope the DNS Server role on any host that does not genuinely need to answer queries, since hosts without the role are not exposed to this code path (trade-off: consolidates DNS onto fewer, higher-value targets); and aggressively restrict who holds even low-level domain credentials, since PR:L means stolen or delegated low-privilege accounts are the entry condition (trade-off: may conflict with operational delegation and service-account usage). Monitor DNS servers for unexpected service crashes or restarts, which are the most likely early symptom of attempts against a memory-corruption defect of this class. No public exploit code was identified and SSVC records no observed exploitation, so treat this as a scheduled, high-priority patch rather than an emergency response, while prioritizing internet-facing or externally reachable DNS servers first.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 20 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerable component is Microsoft's DNS Server (dns.exe / the DNS Server role), which processes DNS queries over UDP/TCP port 53 as well as management traffic through the DNS RPC/administration interfaces. CWE-763, release of an invalid pointer or reference, describes a memory-management defect in which the service frees or dereferences a pointer that is no longer valid - the same general class as use-after-free and double-free conditions. In a network-facing service like DNS, such a defect typically surfaces when a malformed or unexpected request causes the server to act on an object that has already been released, giving the attacker a controlled memory-corruption primitive that can be escalated to code execution inside the DNS service (which normally runs with high privileges). The CVSS vector confirms the practical consequence: PR:L rather than PR:N reflects that the attacker must be an 'authorized' principal per Microsoft's advisory language, but once that bar is met, AC:L and UI:N mean no special conditions or victim interaction are needed and all three of confidentiality, integrity and availability are fully impacted. Notably, the supplied tag for this record reads 'Information Disclosure', which does not align with the high C/I/A impact in the assessed vector or with the description's explicit code-execution outcome; the vector, description and independent assessment are treated here as authoritative. The root-cause context also explains the deployment constraint: workstations and servers that do not have the DNS Server role installed cannot be reached through this code path, which materially shrinks the real-world attack surface compared with a broadly exploitable Windows component.
Know when Windows gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable DNS service (AV:N), low complexity (AC:L), with Microsoft's 'authorized attacker' wording and SSVC supporting PR:L; full code execution yields C/I/A:H, scope unchanged.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Release of invalid pointer or reference in DNS Server allows an authorized attacker to execute code over a network.
Executive ViewAI
A high-severity vulnerability in the Windows DNS Server role (CVE-2026-83889) could allow an authenticated low-privileged attacker to take control of DNS services, disrupting name resolution and potentially enabling broader network compromise. Only organizations running this role on Windows Server 2012-2025 (including Server Core) or Windows 10/11 are affected, but for them, DNS is a critical dependency for authentication and connectivity. With no public exploit identified at time of analysis, leadership should treat this as a high-priority patching item rather than an emergency, yet failure to act could result in service outages or security breaches.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
EUVD-2026-100031
GHSA-932m-cjhf-6vhq
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB