What is the CVSS score of CVE-2026-54128?

CVE-2026-54128 has a CVSS 3.1 base score of 8.4 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Which versions of Windows DHCP Client are affected by CVE-2026-54128?

A use-after-free vulnerability in the Windows DHCP Client service (CVE-2026-54128, CVSS 8.4) affects Windows 10, Windows 11, and Windows Server 2012-2025 across the enterprise.. A patch is available.

Is there a public PoC exploit available for CVE-2026-54128?

Yes, a public proof-of-concept exploit is available for CVE-2026-54128. Prioritise patching immediately. EPSS: 0.3%.

How to fix or mitigate CVE-2026-54128?

Within 24 hours, inventory all Windows 10, 11, and Windows Server (2012-2025) systems and identify mission-critical servers for priority patching. Within 7 days, obtain the Microsoft security patch via the MSRC advisory, test in a non-production environment, and coordinate with infrastructure and operations teams on a phased deployment schedule stratified by system criticality. Within 30 days, complete patch deployment across all affected systems using standard change-management processes, verify successful application per MSRC guidance, and document remediation for audit and compliance records.

Windows DHCP Client CVE-2026-54128

EUVD-2026-44149 HIGH

Use After Free (CWE-416)

2026-07-14 microsoft

GHSA-jxff-hx2c-2gmw

Denial Of Service Use After Free Memory Corruption Microsoft Windows Server 2012 Windows Server 2016 Windows Server 2019 Windows Server 2022 Windows Server 2025 Windows 10 Version 1607 Windows 10 Version 1809 Windows 10 Version 21H2 Windows 10 Version 22H2 Windows Server 2016 Server Core Installation Windows Server 2019 Server Core Installation Windows 11 Version 24H2 Windows 11 Version 25H2 Windows 11 Version 26H1 Windows Server 2025 Server Core Installation Windows Server 2012 Server Core Installation Windows Server 2012 R2 Windows Server 2012 R2 Server Core Installation

8.4

CVSS 3.1 · Vendor: microsoft

Temporal: 7.3

Severity by source

Vendor (microsoft) PRIMARY

8.4 HIGH

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

CIRCL (temporal)

7.3 HIGH

cvss

vuln.today AI

8.4 HIGH

Local trigger with no privileges or interaction (AV:L/AC:L/PR:N/UI:N); use-after-free code execution in the service yields full C/I/A impact within an unchanged scope.

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

4.0 AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 14, 2026 - 19:36 vuln.today

CVE Published

Jul 14, 2026 - 17:08 nvd

HIGH 8.4

DescriptionCVE.org

Use after free in Windows DHCP Client allows an unauthorized attacker to execute code locally.

AnalysisAI

Local code execution in the Windows DHCP Client service stems from a use-after-free (CWE-416) memory-corruption flaw affecting a broad range of Windows 10, Windows 11, and Windows Server releases (Server 2012 through Server 2025). Per the CVSS vector an unauthenticated attacker with local access can achieve high-impact code execution with no user interaction. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; Microsoft has released a patch through the MSRC update guide.

Technical ContextAI

The Windows DHCP Client (Dhcp service / dhcpcore) is the component responsible for acquiring and renewing IP address leases and network configuration from DHCP servers. The root cause is a use-after-free (CWE-416): the code frees a heap object but retains and later dereferences a stale pointer, allowing an attacker who can influence the timing or content of that reuse to corrupt memory and hijack control flow within the service context. The affected CPE set spans client SKUs (Windows 10 1607/1809/21H2/22H2 and Windows 11 24H2/25H2/26H1) and server SKUs (Windows Server 2012, 2012 R2, 2016, 2019, 2022, 2025, including Server Core installations), indicating shared DHCP client code across the Windows platform rather than an edition-specific defect. Tags also reference denial of service, consistent with a memory-corruption bug whose most reliable observable effect is a crash of the client service.

RemediationAI

Patch available per vendor advisory - apply the Microsoft security update for CVE-2026-54128 for each affected SKU as documented at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-54128, which is the primary and recommended fix. Because exact patched build numbers are not included in the input, obtain them from the MSRC update guide entry and deploy the corresponding cumulative update per Windows edition. If patching must be deferred, restrict local access to affected hosts to trusted users (this flaw requires local access per the CVSS vector) and monitor the DHCP client service; note that disabling the DHCP Client service breaks automatic IP configuration and is disruptive on DHCP-dependent networks, so it is only viable on hosts using static addressing. No vendor-published standalone workaround appears in the provided data, so prioritize the update itself.