dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-41108

HIGH · 7.0 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.14393.9234 / 10.0.17763.8880 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Heap-based buffer overflow in Microsoft Windows DNS service allows a locally authorized attacker to overflow a heap-allocated buffer in the DNS server process, enabling arbitrary code execution with elevated (SYSTEM) privileges.

MitigationApply Microsoft security patches for Windows DNS Server when released; until then, limit local server access to trusted administrators only and monitor for suspicious process activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1607Operating system
Affected:< 10.0.14393.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Run 'winver' from command prompt or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows build. Compare the build number against the affected version thresholds provided in the CVE advisory.
    Affected if The installed Windows build is lower than any of these thresholds: 14393.9234 (1607), 17763.8880 (1809), 19044.7417 (21h2), 19045.7417 (22h2), 22631.7219 (23h2), 26100.8655 (24h2), 26200.8655 (25h2), or 28000.2269 (26h1).
  2. Verify DNS Server role is installed
    Open PowerShell and run 'Get-WindowsFeature -Name DNS | Select-Object Name,InstallState' on Windows Server, or check 'Get-WindowsOptionalFeature -Name MicrosoftWindows-DNSServer' on Windows desktop editions to confirm the DNS Server role is present.
    Affected if The DNS Server role shows an InstallState of "Installed" or the feature is enabled.
  3. Confirm DNS Server service is running
    Run 'sc query dns' from an elevated command prompt, or use PowerShell 'Get-Service -Name DNS* | Select-Object Name,Status' to check if the DNS service is currently active.
    Affected if The DNS service shows a Status of "RUNNING" indicating the vulnerable component is loaded in memory.
  4. Check DNS Server service executable version
    Locate the dns.exe binary (typically in C:\Windows\System32\dns.exe) and run 'Get-Item C:\Windows\System32\dns.exe | Select-Object Version,FileVersion' to retrieve the file version.
    Affected if The dns.exe file version is lower than the version bundled with the patched security update for this CVE.

A system is affected if it runs any of the listed Windows versions with a build below the specified thresholds AND has the DNS Server role installed with the DNS service actively running.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.14393.9234 / 10.0.17763.8880 / 10.0.19044.7417 or later
Fixed in 10.0.14393.923410.0.17763.888010.0.19044.7417
Interim mitigation

Apply Microsoft security patches for Windows DNS Server when released; until then, limit local server access to trusted administrators only and monitor for suspicious process activity.

Recommended fix High confidence

Upgrade to the minimum fixed build for your Windows release: Windows 10 1607 to build 10.0.14393.9234, Windows 10 1809 to build 10.0.17763.8880, Windows 10 21h2 to build 10.0.19044.7417, Windows 10 22h2 to build 10.0.19045.7417, Windows 11 23h2 to build 10.0.22631.7219, Windows 11 24h2 to build 10.0

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows 10 or 11 release channel you are on (e.g., 1607, 1809, 21h2, 22h2, 23h2, 24h2, 25h2, 26h1)
  3. Open Windows Settings > Update & Security > Windows Update
  4. Click 'Check for updates' to download and install the latest security updates
  5. Alternatively, manually update by downloading the specific cumulative update for your Windows version from the Microsoft Update Catalog
  6. After installation, verify the build number matches or exceeds the fixed version: Windows 10 1607 requires 10.0.14393.9234, Windows 10 1809 requires 10.0.17763.8880, Windows 10 21h2 requires 10.0.19044.7417, Windows 10 22h2 requires 10.0.19045.7417, Windows 11 23h2 requires 10.0.22631.7219, Windows 11 24h2 requires 10.0.26100.8655, Windows 11 25h2 requires 10.0.26200.8655, Windows 11 26h1 requires
  7. Restart the system to complete the update process
Caveat Standard Windows update risks apply: possible compatibility issues with legacy software, potential need to reinstall affected applications, and brief system downtime for restart

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,140
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,024.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41108 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data