CVE-2026-118737: Windows RPC Runtime Cryptographic Signature Verification Remote Code Execution
- Vendor
- Microsoft Corporation
CVE-2026-118737 is a critical remote code execution vulnerability in Windows Remote Procedure Call Runtime caused by improper verification of cryptographic signatures. An unauthenticated network attacker can exploit a timing-dependent authentication weakness involving a pending DNS query by winning a race condition, without user interaction. The vulnerability has a CVSS v3.1 base score of 8.1, and Microsoft assesses exploitation as less likely. Windows updates released beginning November 10, 2026, address the vulnerability and introduce related NTLM protections that establish cryptographic session keys and negotiate genuine message signing rather than relying on the non-cryptographic legacy ALWAYS_SIGN placeholder.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits unauthenticated remote code execution on an affected Windows server, with potentially high impacts to confidentiality, integrity, and availability. The execution security context is not specified. Confirmed wormability and active exploitation are not established.
Mitigation
If you can’t patch tonight, do this now.
After installing the November 2026 protections, audit NTLM signing compatibility and consider enabling early server-side enforcement by setting ServerRequireNtlmSign to 1. This rejects unsigned clients and reduces relay exposure; validate application compatibility first. On Windows Server 2019 and later with NTLM Enhanced auditing, inspect client Event ID 4022 and server Event ID 4023 for negotiated signing flags and session-key availability, rather than relying on event severity. Keep ClientAllowUnsignedNtlm at its default value of 0 so clients offer signing. These settings require no restart. Anonymous and guest sessions remain exempt. A separate, fully protective pre-update workaround is not specified.
Remediation
Patch, then assume compromise.
Install the Microsoft security update addressing CVE-2026-118737 for each affected Windows release, using the per-CVE update guidance to determine the applicable package. Relevant Windows protections began shipping on November 10, 2026; exact per-release fixed builds are not available here. Account for the staged NTLM signing rollout: initially, updated clients offer signing by default, but servers still accept unsigned clients. Server-side signing enforcement is scheduled to become the default in May 2027.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-118737 exploited in the wild?
- As of Nov 12, 2026, Mallory has no reports of CVE-2026-118737 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-118737?
- As of Nov 12, 2026, Mallory has found no public exploit for CVE-2026-118737.
- Is there a patch for CVE-2026-118737?
- Install the Microsoft security update addressing CVE-2026-118737 for each affected Windows release, using the per-CVE update guidance to determine the applicable package. Relevant Windows protections began shipping on November 10, 2026; exact per-release fixed builds are not available here.
- What products are affected by CVE-2026-118737?
- Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, Microsoft Corporation Windows 11 23h2, and 8 more.
- How severe is CVE-2026-118737?
- CVE-2026-118737 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.71% (54th percentile) as of Nov 12, 2026.
Recent activity
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.