CVE-2025-54110: CVE-2025-54110: Integer overflow or wraparound in Windows Kernel allows an authorized attacker to elevate …

What it is

Integer overflow or wraparound in Windows Kernel allows an authorized attacker to elevate privileges locally.

Exploitation evidence

First exploit evidence seen: 2025-11-19 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

1 public repositories from 1 accounts, first seen 2025-11-19. Most starred: canomer/CVE-2025-54110-Kernel-EoP-PoC (11 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

• microsoft windows 10 1507: upgrade to 10.0.10240.21128 or later
• microsoft windows 10 1607: upgrade to 10.0.14393.8422 or later
• microsoft windows 10 1809: upgrade to 10.0.17763.7792 or later
• microsoft windows 10 21h2: upgrade to 10.0.19044.6332 or later
• microsoft windows 10 22h2: upgrade to 10.0.19045.6332 or later
• microsoft windows 11 22h2: upgrade to 10.0.22621.5909 or later
• microsoft windows 11 23h2: upgrade to 10.0.22631.5909 or later
• microsoft windows 11 24h2: upgrade to 10.0.26100.6508 or later
• microsoft windows server 2016: upgrade to 10.0.14393.8422 or later
• microsoft windows server 2019: upgrade to 10.0.17763.7792 or later
• microsoft windows server 2022: upgrade to 10.0.20348.4106 or later
• microsoft windows server 2022 23h2: upgrade to 10.0.25398.1849 or later
• microsoft windows server 2025: upgrade to 10.0.26100.6508 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

• https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-54110 (Vendor Advisory)

MITRE ATT&CK mitigations for this chain

• M1050 Exploit Protection (for T1203) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
• M1051 Update Software (for T1203) : Perform regular software updates to mitigate exploitation risk. Keeping software up-to-date with the latest security patches helps prevent adversaries from exploiting known vulnerabilities in client software, reducing the risk of successful attacks.
• M1048 Application Isolation and Sandboxing (for T1203) : Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist. Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. Risks of additional exploits and weaknesses in those systems may still exist.

Detection Generic guidance

• Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.