Quick answers
- Is CVE-2026-50683 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50683 being exploited in the wild.
- How severe is CVE-2026-50683?
- High severity, with a CVSS score of 8, published 14 July 2026.
- Which products and versions are affected?
- Microsoft Windows 10 < 10.0.14393.9339; Microsoft Windows Server 2012 6.2.9200.26226 / 6.3.9600.23291; Microsoft Windows Server 2016 10.0.14393.9339 / 10.0.17763.9020.
- Is there a fix for CVE-2026-50683?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-50683 attacked?
- It is attacked from the adjacent network, in an operating system.
- Am I affected by CVE-2026-50683?
- Check whether you run Microsoft Windows Server 2012 R2, Microsoft Windows 10, Microsoft Windows Server 2012 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap-based buffer overflow (CWE-122) exists in the Microsoft Windows DHCP Server service. The vulnerability is triggered when the server improperly handles specially crafted DHCP packets. An attacker must be authenticated and located on an adjacent network (the same local subnet) to exploit the flaw. Successful exploitation allows for local privilege escalation, potentially leading to full system compromise. Microsoft has released security updates for affected versions of Windows 10 and Windows Server (2012 through 2019).
Affected products
- Microsoft Windows 10 Version 1607 < 10.0.14393.9339
- Microsoft Windows 10 Version 1809 < 10.0.17763.9020
- Microsoft Windows Server 2012 / 2012 R2 6.2.9200.26226 / 6.3.9600.23291
- Microsoft Windows Server 2016 / 2019 10.0.14393.9339 / 10.0.17763.9020
Timeline
- 2026-07-14: disclosed
- 2026-07-14: advisory