CVE-2026-21525: Windows Remote Access Connection Manager denial of service

Quick Answer

CVE-2026-21525 is a local denial-of-service flaw in Windows Remote Access Connection Manager. Microsoft describes an unauthorized local attacker triggering a NULL-pointer dereference, not remote code execution. Inventory Windows editions, preserve RasMan service and endpoint evidence, and install the applicable February update below. A service failure alone does not prove exploitation, and restarting it is not a fix.

Evidence check: Vendor evidence and unresolved limits are described below. CISA KEV catalog 2026.10.02 was checked October 2. Catalog additions, vendor publication dates and update releases are separate events. No exploit, installation or recovery test is claimed.

Context

Status At A Glance

Product scope	Microsoft — Windows
CVE	CVE-2026-21525
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-02-10
Vendor severity	Moderate
CVSS	6.2 (CVSS v3.1 base)
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	No in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWE	CWE-476
Federal remediation date	2026-03-03 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Microsoft Windows NULL Pointer Dereference Vulnerability. Microsoft Windows Remote Access Connection Manager contains a NULL pointer dereference that could allow an unauthorized attacker to deny service locally. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Match the installed Windows edition, architecture and servicing type to the product-specific RasMan update rows below. Do not infer exposure from the words Remote Access or assume all historical products remain supported.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

1. Confirm. Inventory every Windows asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Microsoft advisory.
4. Remediate. Install the applicable February 2026 or later Windows cumulative update and verify the resulting build.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Investigation And Recovery

The NULL-pointer dereference permits a local denial of service. CISA lists the CVE as known exploited; review service crashes and related endpoint telemetry on systems that were vulnerable.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: The checked Microsoft CVRF marks Exploited: Yes. This is the retrieved vendor assessment, not a claim that an archived initial-publication version was independently verified. CISA's catalog chronology is listed separately below.

CISA statement: CVE-2026-21525 was added to KEV on 2026-02-10. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Microsoft security advisory
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2026-21525 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.