Skip to content
Server Security Center
KEVhigh7.8

CVE-2025-21333: Microsoft Windows Hyper-V NT Kernel Integration VSP Heap-based Buffer Overflow

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-01-14.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
10%
higher than 95.7% of all CVEs
Added to CISA KEV
2025-01-14
US federal due date 2025-02-04
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-21333 explained

CVE-2025-21333 is a heap-based buffer overflow in the Hyper-V NT Kernel Integration VSP component of Microsoft Windows. A local attacker with low privileges can use it to gain SYSTEM privileges. CISA lists it as known to be exploited, so affected Windows clients and servers should be patched promptly.

Impact

An attacker who can already run code locally with low privileges can escalate to SYSTEM without user interaction. This gives full control over confidentiality, integrity and availability of the affected system. CISA rates the technical impact as total but not automatable, meaning exploitation needs local access rather than mass remote attacks. Attackers are known to use this vulnerability. Use in ransomware campaigns is listed as unknown.

Who is affected

The CVE record lists Windows 10 Version 21H2 before 10.0.19044.5371 and 22H2 before 10.0.19045.5371. It lists Windows 11 version 22H2 before 10.0.22621.4751, and 22H3 and Version 23H2 before 10.0.22631.4751. Windows 11 Version 24H2 is affected before 10.0.26100.2894. Windows Server 2022, 23H2 Edition (Server Core installation) is affected before 10.0.25398.1369. Windows Server 2025, including Server Core, is affected before 10.0.26100.2894. These listed builds contain the fix.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Windows Hyper-V NT Kernel Integration VSP contains a heap-based buffer overflow vulnerability that allows a local attacker to gain SYSTEM privileges.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 21H2x64
    Affected
    • < 10.0.19044.5371
    Fixed in
    • 10.0.19044.5371
  • Microsoft Windows 10 Version 22H2x64
    Affected
    • < 10.0.19045.5371
    Fixed in
    • 10.0.19045.5371
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.4751
    Fixed in
    • 10.0.22621.4751
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.4751
    Fixed in
    • 10.0.22631.4751
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.4751
    Fixed in
    • 10.0.22631.4751
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.2894
    Fixed in
    • 10.0.26100.2894
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1369
    Fixed in
    • 10.0.25398.1369
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.2894
    Fixed in
    • 10.0.26100.2894
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.2894
    Fixed in
    • 10.0.26100.2894

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5371
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5371
    • Microsoft Windows 11 version 22H2: 10.0.22621.4751
    • Microsoft Windows 11 version 22H3: 10.0.22631.4751
    • Microsoft Windows 11 Version 23H2: 10.0.22631.4751
    • Microsoft Windows 11 Version 24H2: 10.0.26100.2894
    Fixed versions for 3 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21333
  • CISA's deadline for US federal agencies: 2025-02-04 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install Microsoft's security update that brings each affected system to the fixed build listed for its Windows version.
  2. Prioritize systems where untrusted or many users can log on locally, as the attack requires local access.
  3. Verify installed build numbers across your fleet to confirm the update applied.
  4. Limit local logon rights and remove unnecessary accounts to reduce who could attempt privilege escalation.
  5. Check systems for signs of compromise, such as unexpected SYSTEM-level processes or new privileged accounts.
  6. Follow Microsoft's advisory and CISA's required action; U.S. federal agencies must remediate by 2025-02-04.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-122 Heap-based Buffer Overflow

Questions about CVE-2025-21333

Is CVE-2025-21333 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-01-14. Whether it has been used in ransomware campaigns is listed as unknown.
Can it be exploited remotely?
No. The attack vector is local. An attacker needs low-privileged access to the system first, then can escalate to SYSTEM privileges without user interaction.
Which builds fix the issue?
Fixed builds include 10.0.19044.5371 and 10.0.19045.5371 for Windows 10, and 10.0.22621.4751 and 10.0.22631.4751 for Windows 11. Windows 11 24H2 and Windows Server 2025 are fixed in 10.0.26100.2894, and Windows Server 2022, 23H2 Edition in 10.0.25398.1369.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.