dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-48564

HIGH · 8.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

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 Windows DHCP Server allows an authorized attacker to execute code over a network.

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

A heap-based buffer overflow vulnerability in Windows DHCP Server allows an authenticated remote attacker to execute arbitrary code by sending specially crafted DHCP packets. The vulnerability stems from improper memory handling when processing DHCP request messages.

MitigationApply Microsoft security patches for Windows DHCP Server immediately. If patches are unavailable, restrict network access to DHCP servers and monitor for anomalous DHCP traffic as a compensating control.

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.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.9339
Windows Server 2019Operating system
Affected:< 10.0.17763.9020
Windows Server 2022Operating system
Affected:< 10.0.20348.5386
Windows Server 2025Operating system
Affected:< 10.0.26100.33158

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Verify DHCP Server role is installed
    Run 'Get-WindowsFeature -Name DHCP' in PowerShell on Windows Server, or check Services list for 'DHCP Server' service on any Windows system
    Affected if DHCP Server role or service is present on the system
  2. Identify Windows version and build number
    Run 'winver' from command prompt, or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' from command prompt, or run 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayerBuildNumber' in PowerShell
    Affected if The system runs an affected Windows version: 10 1607, 10 1809, Server 2012/R2, Server 2016, Server 2019, Server 2022, or Server 2025 with build numbers below the thresholds
  3. Confirm build number is in vulnerable range
    Compare the installed build number against these thresholds: Windows 10 1607/Server 2016: below 14393.9339; Windows 10 1809/Server 2019: below 17763.9020; Server 2022: below 20348.5386; Server 2025: below 26100.33158; Server 2012/R2: all versions are affected
    Affected if The installed build number is lower than the fixed version for the respective Windows release
  4. Verify DHCP service is running and reachable
    Run 'Get-Service -Name DHCPServer' in PowerShell or check Services console to confirm DHCP Server service status; check network listening with 'netsh dhcpserver show server'
    Affected if DHCP Server service is running and the server is active on the network, exposing the vulnerability if version is affected
  5. Check for recent security updates
    Run 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' in PowerShell to list recent security patches
    Affected if No recent security updates have been installed, or the specific KB for this CVE is absent

The system is affected if it runs a vulnerable Windows version with the DHCP Server role installed and the build number falls below the fixed threshold for that Windows release.

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.9339 / 10.0.17763.9020 / 10.0.20348.5386 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.20348.5386
Interim mitigation

Apply Microsoft security patches for Windows DHCP Server immediately. If patches are unavailable, restrict network access to DHCP servers and monitor for anomalous DHCP traffic as a compensating control.

Recommended fix High confidence

Upgrade to the build numbers listed: Windows 10 1607 to 10.0.14393.9339+, Windows 10 1809 to 10.0.17763.9020+, Windows Server 2016 to 10.0.14393.9339+, Windows Server 2019 to 10.0.17763.9020+, Windows Server 2022 to 10.0.20348.5386+, Windows Server 2025 to 10.0.26100.33158+, or migrate from Server 2

  1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
  2. Confirm the DHCP Server role is installed via Server Manager > Manage > Add Roles and Features > DHCP Server
  3. For Windows 10: Install the latest cumulative update from Windows Update or manually download from Microsoft Update Catalog
  4. For Windows Server: Run Windows Update or use WSUS to install the latest security update, or manually download the applicable cumulative update from Microsoft Update Catalog
  5. After update installation, restart the server to apply changes
  6. Verify the fix by checking the installed build number matches or exceeds: 10.0.14393.9339 (1607/Server 2016), 10.0.17763.9020 (1809/Server 2019), 10.0.20348.5386 (Server 2022), or 10.0.26100.33158 (Server 2025)
  7. For Windows Server 2012/R2: Apply the applicable security update from the Microsoft Security Response Center; if no update available, consider migrating to a supported Windows Server version
Caveat Standard Windows cumulative update considerations apply; test updates in non-production environments first; Server 2012/R2 is end-of-support so migrating to a newer Server version may require application compatibility testing

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48564 — 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-48564 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