Skip to content
Server Security Center
KEVmedium6.2

CVE-2026-21525: Microsoft Windows NULL Pointer Dereference

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2026-02-10.

CVSS v3.1 (CVE record)
6.2
medium
EPSS (exploit probability, 30 days)
5.0%
higher than 92.4% of all CVEs
Added to CISA KEV
2026-02-10
US federal due date 2026-03-03
Automatable (CISA SSVC)
no
technical impact: partial

CVE-2026-21525 explained

CVE-2026-21525 is a NULL pointer dereference in the Windows Remote Access Connection Manager. It lets an unauthorized local attacker cause a denial of service on affected Windows client and server versions. CISA lists it as known exploited, so attackers are known to use it.

Impact

An attacker with local access can crash the affected service and cause a denial of service. The attack needs no privileges, no user interaction and has low complexity. Confidentiality and integrity are not affected; availability impact is high. CISA's SSVC rates it as not automatable, with partial technical impact. CISA lists it in its Known Exploited Vulnerabilities catalog; known ransomware use is listed as unknown.

Who is affected

The CVE record lists Windows 10 Version 1607, 1809, 21H2 and 22H2, Windows 11 version 22H3, 23H2, 24H2, 25H2 and 26H1, Windows Server 2012 (including Server Core) and Windows Server 2012 R2. Fixed builds include 10.0.14393.8868, 10.0.17763.8389, 10.0.19044.6937, 10.0.19045.6937, 10.0.22631.6649, 10.0.26100.7840, 10.0.26200.7840, 10.0.28000.1575, 6.2.9200.25923 and 6.3.9600.23022. Further products are listed on this page.

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

Official description

Null pointer dereference in Windows Remote Access Connection Manager allows an unauthorized attacker to deny service locally.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, 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 160732-bit, x64
    Affected
    • < 10.0.14393.8868
    Fixed in
    • 10.0.14393.8868
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.8389
    Fixed in
    • 10.0.17763.8389
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.6937
    Fixed in
    • 10.0.19044.6937
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.6937
    Fixed in
    • 10.0.19045.6937
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.6649
    Fixed in
    • 10.0.22631.6649
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.6649
    Fixed in
    • 10.0.22631.6649
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.7840
    Fixed in
    • 10.0.26100.7840
  • Microsoft Windows 11 Version 25H2
    Affected
    • < 10.0.26200.7840
    Fixed in
    • 10.0.26200.7840
  • Microsoft Windows 11 version 26H1ARM64
    Affected
    • < 10.0.28000.1575
    Fixed in
    • 10.0.28000.1575
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25923
    Fixed in
    • 6.2.9200.25923
Show 11 more products
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25923
    Fixed in
    • 6.2.9200.25923
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.23022
    Fixed in
    • 6.3.9600.23022
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.23022
    Fixed in
    • 6.3.9600.23022
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.8868
    Fixed in
    • 10.0.14393.8868
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.8868
    Fixed in
    • 10.0.14393.8868
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.8389
    Fixed in
    • 10.0.17763.8389
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.8389
    Fixed in
    • 10.0.17763.8389
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.4773
    Fixed in
    • 10.0.20348.4773
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.2149
    Fixed in
    • 10.0.25398.2149
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.32370
    Fixed in
    • 10.0.26100.32370
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.32370
    Fixed in
    • 10.0.26100.32370

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1607: 10.0.14393.8868
    • Microsoft Windows 10 Version 1809: 10.0.17763.8389
    • Microsoft Windows 10 Version 21H2: 10.0.19044.6937
    • Microsoft Windows 10 Version 22H2: 10.0.19045.6937
    • Microsoft Windows 11 version 22H3: 10.0.22631.6649
    • Microsoft Windows 11 Version 23H2: 10.0.22631.6649
    Fixed versions for 15 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21525
  • CISA's deadline for US federal agencies: 2026-03-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install Microsoft's security update so each system reaches the fixed build listed for its Windows version, for example 10.0.26100.7840 for Windows 11 Version 24H2.
  2. Prioritize patching because CISA lists this vulnerability as known exploited; US federal agencies must remediate by 2026-03-03.
  3. Follow the Microsoft advisory for any mitigations, and discontinue use of the product if mitigations are unavailable, per CISA's required action.
  4. Limit local and interactive access to affected systems to trusted users.
  5. Check affected systems for unexpected crashes or service outages that may indicate attempts to exploit this issue.

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
Partial – limited control or information

Weakness: CWE-476 NULL Pointer Dereference

Questions about CVE-2026-21525

Can this be exploited remotely?
The CVSS vector rates the attack as local. The description says an unauthorized attacker can deny service locally. No privileges or user interaction are required.
Does this vulnerability expose data or allow code execution?
No. The CVSS ratings show no confidentiality or integrity impact. The impact is on availability, through denial of service.
Is this being exploited?
Yes. CISA added CVE-2026-21525 to its Known Exploited Vulnerabilities catalog on 2026-02-10. Whether it is used in ransomware campaigns is listed as unknown.

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.