dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-44815

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Stack-based buffer overflow in Windows DHCP Client allows an unauthorized 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

Stack-based buffer overflow in Windows DHCP Client allows an unauthenticated remote attacker to execute arbitrary code over the network by sending specially crafted DHCP responses.

MitigationApply Microsoft security updates for Windows DHCP Client when available; until then, consider network segmentation to limit exposure and disable DHCP client services if not required.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 Client service status
    Run 'Get-Service Dhcp' in PowerShell or 'sc query dhcp' in Command Prompt to check if the DHCP Client service is installed and running.
    Affected if The DHCP Client service is installed and running (vulnerability only applies when the service is active).
  2. Obtain Windows build number
    Run 'winver' or execute 'systeminfo | findstr /B /C:"OS Version"' to retrieve the exact Windows build number.
    Affected if The displayed build number is lower than any of the following: 14393.9234 (Windows 10 1607), 17763.8880 (Windows 10 1809), 19044.7417 (Windows 10 21h2/22h2), 22631.7219 (Windows 11 23h2), 26100.8655 (Windows 11 24h2/25h2), or 28000.2269 (Windows 11 26h1).
  3. Confirm network exposure
    Determine if the system is directly connected to untrusted networks where malicious DHCP responses could be injected (e.g., public Wi-Fi, bridged networks).
    Affected if The system receives DHCP responses from untrusted or attacker-controlled network segments.

The system is affected if the DHCP Client service is running AND the Windows build number falls below the fixed versions listed for the respective 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.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 updates for Windows DHCP Client when available; until then, consider network segmentation to limit exposure and disable DHCP client services if not required.

Recommended fix High confidence

Upgrade to the Windows build version >= the threshold for your respective release (e.g., Windows 10 22h2 to build 10.0.19045.7417 or later, Windows 11 24h2 to build 10.0.26100.8655 or later)

  1. Check current Windows build version by running `winver` or `systeminfo | findstr /B /C:"OS Version"`
  2. Open Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest cumulative update
  4. Verify the update installed successfully by checking that the build number matches or exceeds: Windows 10 1607: 10.0.14393.9234 | Windows 10 1809: 10.0.17763.8880 | Windows 10 21h2: 10.0.19044.7417 | Windows 10 22h2: 10.0.19045.7417 | Windows 11 23h2: 10.0.22631.7219 | Windows 11 24h2: 10.0.26100.8655 | Windows 11 25h2: 10.0.26200.8655 | Windows 11 26h1: 10.0.28000.2269
  5. Confirm the DHCP Client service (Dhcp) is running and the vulnerability is remediated
Caveat Standard Windows cumulative updates typically have minimal risk; test in staging if running line-of-business applications dependent on specific DHCP behavior

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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