What is the CVSS score of EUVD-2026-43985?

EUVD-2026-43985 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Windows DNS are affected by EUVD-2026-43985?

CVE-2026-49175 affects Microsoft Windows DNS across Windows 10, 11, and Server 2022/2025, with no publicly known exploits currently identified.. A patch is available.

How to fix or mitigate EUVD-2026-43985?

Within 24 hours, inventory all Windows 10, Windows 11, Windows Server 2022, and Windows Server 2025 systems and identify DNS-critical infrastructure including domain controllers. Deploy vendor-released patches to all critical systems within 7 days through Windows Update or WSUS. Complete patch deployment to all remaining affected systems within 30 days and validate successful application.

Windows DNS EUVD-2026-43985

| CVE-2026-49175 HIGH

Heap-based Buffer Overflow (CWE-122)

2026-07-14 microsoft

GHSA-rmfg-jhvq-w5r5

Buffer Overflow Heap Overflow Microsoft Windows Server 2022 Windows Server 2025 Windows 10 Version 21H2 Windows 10 Version 22H2 Windows 11 Version 24H2 Windows 11 Version 25H2 Windows 11 Version 26H1 Windows Server 2025 Server Core Installation

7.8

CVSS 3.1 · Vendor: microsoft

Temporal: 6.8

Severity by source

Vendor (microsoft) PRIMARY

7.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CIRCL (temporal)

6.8 MEDIUM

cvss

vuln.today AI

7.8 HIGH

Description states local privilege elevation by an authorized attacker, so AV:L and PR:L; low complexity and full host compromise give AC:L and C/I/A:H with unchanged scope.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 14, 2026 - 17:42 vuln.today

CVE Published

Jul 14, 2026 - 17:04 nvd

HIGH 7.8

DescriptionCVE.org

Heap-based buffer overflow in Windows DNS allows an authorized attacker to elevate privileges locally.

AnalysisAI

Local privilege escalation in Microsoft Windows DNS lets an already-authenticated, low-privileged attacker corrupt heap memory to gain higher (likely SYSTEM) privileges on affected Windows 10, Windows 11, and Windows Server 2022/2025 systems. The flaw is a heap-based buffer overflow (CWE-122) reported by Microsoft itself, with a vendor patch available via MSRC. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, so it currently represents a patch-priority rather than an emergency.

Technical ContextAI

The vulnerability lives in the Windows DNS component (the DNS Server role and/or associated DNS resolution code shipped with Windows client and server SKUs). CWE-122 (heap-based buffer overflow) indicates that attacker-influenced data is written past the bounds of a dynamically allocated heap buffer, corrupting adjacent heap structures. Successful heap grooming and overflow can overwrite function pointers or object metadata, allowing an attacker to redirect execution or manipulate privileged data structures. Per the CPE data the flaw spans Windows 10 (21H2, 22H2), Windows 11 (24H2, 25H2, 26H1), and Windows Server 2022 and 2025 including Server Core installations, indicating the vulnerable code is in a broadly shared Windows DNS binary rather than an edition-specific feature.

RemediationAI

Apply the Microsoft security update for CVE-2026-49175 (Patch available per vendor advisory) referenced at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-49175; install the corresponding monthly cumulative update for each affected SKU, prioritizing Windows Server 2022/2025 hosts running the DNS Server role and any multi-user or session-host systems where local footholds are likely. Exact fixed build numbers are listed per edition in the MSRC entry - deploy them via Windows Update, WSUS, or your patch management tooling. Because exploitation is local and requires an existing low-privileged account, in the interim reduce risk by tightening local logon and interactive-session access, removing unnecessary local accounts, and restricting who can run code on DNS servers and domain infrastructure; note these are access-hardening controls that limit the pool of potential attackers but do not remove the underlying overflow, so patching remains the only definitive fix.