Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local session on DNS server
-
ExploitInvoke DNS Server operation lacking proper authorization check
-
ExecutionTamper with DNS records or configuration
-
ImpactIntegrity compromise of name resolution
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the Windows DNS Server role to be installed and running, and the attacker must already possess a local, low-privileged account or interactive/logon session on that DNS server host (AV:L, PR:L). Exploitation is LIMITED by these prerequisites: it is not remotely reachable over the network, cannot be performed by a fully unauthenticated actor, and needs no victim user interaction. Impact is confined to integrity (tampering with DNS data/configuration); there is no confidentiality disclosure or denial of service per the CVSS vector. Affected builds span Windows Server 2012 through 2025 (including Server Core installations) and Windows 10 1607/1809 below the patched build numbers listed by the vendor. |
| Impact | This is a genuine but moderate-priority issue, not a top-tier emergency. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N, base 5.5 Medium) tells a consistent story: exploitation requires LOCAL access and at least low-level existing privileges (PR:L) on the DNS Server host, with no user interaction, and yields a HIGH integrity impact but NO confidentiality or availability impact - matching the description's 'authorized attacker performing tampering locally.' All signals align downward: CISA SSVC rates Exploitation as 'none' (no observed or public exploitation), Automatable as 'no' (cannot be reliably scripted at scale, consistent with the local/authenticated vector), and Technical Impact as 'partial' (not total system control). There is no CISA KEV listing and no POC referenced in the data, so there is no public exploit identified at time of analysis. No EPSS score was provided, so exploitation probability cannot be quantified from the input. The practical risk is an authenticated local user tampering with DNS configuration/records (integrity) rather than remote mass exploitation - treat it as a standard patch-cycle item, prioritized where untrusted users have local/low-privilege access to DNS servers. The CVSS vector, description (both local/authorized), and SSVC are mutually consistent; no contradictory signals were found in the provided data. |
| Exploit ScenarioDerived | An attacker who already holds a low-privileged local account or session on a Windows Server running the DNS Server role abuses an incorrect-authorization flaw (CWE-863) to tamper with DNS data or configuration they should not be able to modify. No remote access, user interaction, or administrative rights are required beyond the initial low-privilege foothold. No public proof-of-concept or active exploitation is referenced in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Incorrect authorization in the Windows DNS Server role allows an attacker who already holds a low-privileged local account or interactive logon session on the DNS host to tamper with DNS data or service configuration, degrading integrity with no confidentiality or availability impact. Affected systems span Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025 (including Server Core installations) plus Windows 10 versions 1607 and 1809, in each case below the vendor's patched build numbers. Microsoft has released a fix, and no public exploit code has been identified at time of analysis; the SSVC assessment records exploitation as 'none', automatable as 'no' and technical impact as 'partial', so this is a genuine but moderate-priority issue rather than a top-tier emergency.
RemediationAI
Microsoft has released fixes through the MSRC security update for CVE-2026-70083 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70083); apply the current cumulative update so affected hosts reach at least the following vendor-listed builds, which are the upper bounds of the vulnerable ranges: Windows Server 2012 6.2.9200.26434, Windows Server 2012 R2 6.3.9600.23470, Windows Server 2016 and Windows 10 1607 10.0.14393.9612, Windows Server 2019 and Windows 10 1809 10.0.17763.9376, Windows Server 2022 10.0.20348.5761, and Windows Server 2025 10.0.26100.33650. Because exploitation requires a local, low-privileged account or interactive logon on the DNS host (CVSS AV:L/PR:L), the practical compensating controls are host-side access discipline: remove or disable unnecessary local accounts and remote-interactive access on DNS servers (side effect: reduced administrative convenience for break-glass and maintenance access), restrict who can log on locally to the DNS role holders and audit those sessions, and remove the DNS Server role entirely from hosts that do not need to resolve or host zones (side effect: loss of a functional dependency elsewhere in the environment). Network-level mitigations such as firewall rules are not relevant here, since the flaw is not remotely reachable; the effective control surface is local privilege and interactive-logon exposure. No public exploit code has been identified and the CISA SSVC assessment marks the issue as non-automatable with only partial technical impact, so patching can be scheduled with the normal monthly cycle rather than treated as an emergency, though integrity of DNS records on internet- or AD-facing resolvers makes timely rollout advisable.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 13 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 vulnerability is an instance of CWE-863 (Incorrect Authorization) in the DNS Server role of Windows Server and the corresponding Windows 10 client builds, reported to Microsoft by secure@microsoft.com. In this class of bug, an operation that should be gated behind a stronger privilege check is instead reachable by a principal holding lesser rights, so the service performs an action the caller was never meant to be authorized for - here, modification of DNS records or service configuration. The CVSS vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N is decisive about the exposure model: AV:L means the attacker must already be executing locally on the DNS host, PR:L means a low-privileged authenticated account or session is required, UI:N means no victim interaction, and the scope-unchanged impact is integrity-only (I:H) with C:N and A:N. In other words, this is an elevation-of-privilege-style authorization gap reachable only after some local foothold on a server that has the DNS Server role installed and running, not a remotely exploitable DNS-protocol flaw. EUVD entries (EUVD-2026-99153) enumerate the vulnerable builds by kernel version rather than by CPE string, covering the 6.2.9200.x, 6.3.9600.x, 10.0.14393.x, 10.0.17763.x, 10.0.20348.x and 10.0.26100.x families.
Know when Windows 10 1607 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:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Description states local tampering by an authorized attacker, so AV:L and PR:L; integrity-only impact gives I:H with C:N/A:N and unchanged scope.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Incorrect authorization in DNS Server allows an authorized attacker to perform tampering locally.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-99153
GHSA-633j-7wp2-fh6g
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB