CVE-2026-50683
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 · uneditedHeap-based buffer overflow in Windows DHCP Server allows an authorized attacker to elevate privileges over an adjacent network.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
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 confidenceHeap-based buffer overflow vulnerability in Windows DHCP Server enables an authenticated attacker with network access to execute arbitrary code and elevate privileges. The flaw exists in the DHCP server component processing malformed packets, allowing code execution in the context of the DHCP service account.
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< 10.0.14393.9339< 10.0.17763.9020all versions= r2< 10.0.14393.9339< 10.0.17763.9020< 10.0.20348.5386< 10.0.26100.33158CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Verify DHCP Server role is installedRun 'Get-WindowsFeature -Name DHCP' in PowerShell on Windows Server, or check 'DHCP Server' in Windows Features on Windows 10. Alternatively, check for the DhcpServer service via 'Get-Service DhcpServer' in PowerShell.Affected if DHCP Server role or DhcpServer service is present on the system
-
Check Windows build numberRun 'winver' or execute 'Get-ComputerInfo | Select-Object OsVersion, OsBuildNumber' in PowerShell to obtain the exact build number.Affected if Build number falls within the affected ranges: < 10.0.14393.9339 (Windows 10 1607/Server 2016), < 10.0.17763.9020 (Windows 10 1809/Server 2019), all versions of Server 2012/2012 R2, < 10.0.20348.5386 (Server 2022), or < 10.0.26100.33158 (Server 2025)
-
Confirm DHCP service is runningRun 'Get-Service DhcpServer' in PowerShell and check the Status field, or use 'sc query DhcpServer'.Affected if The DhcpServer service is in a Running state, making the vulnerable component active
-
Verify DHCP server bindings and listening configurationRun 'Get-DhcpServerv4Binding' or 'Get-DhcpServerv6Binding' in PowerShell to see which network interfaces the DHCP server is bound to.Affected if DHCP server is bound to active network interfaces, exposing the service to network packets
A system is affected if it runs a vulnerable Windows version within the specified build ranges AND has the DHCP Server role installed with the DhcpServer service running and bound to network interfaces.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data10.0.14393.933910.0.17763.902010.0.20348.5386
Apply Microsoft security updates for Windows DHCP Server when released; limit DHCP service accounts to minimum required privileges and restrict network access to trusted administrative segments.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50683 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50683 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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