Skip to main content
Mallory
HighVulnerability

CVE-2026-118737: Windows RPC Runtime Cryptographic Signature Verification Remote Code Execution

Published Nov 10, 2026 · Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days14 mentions · peak 6 in a dayToday
CVSS8.1High · v3.1
EPSS0.71%54th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-118737CWE-347 · Improper Verification of…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows 11 Version 26H2 For Arm64-Based Systemsapplication
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2025operating_system
FAQ

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.
Activity feed

Recent activity

16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
the hacker newsNews · Nov 12, 2026ThreatsDay: 59 Linux Kernel Bugs, Falcon Spyware, GSocket Backdoors + 17 More StoriesA Windows Remote Procedure Call Runtime vulnerability that could allow an unauthorized attacker to execute code over a network. Microsoft released updates that strengthen NTLM session-key establishment and message signing to reduce relay exposure; Windows servers will require NTLM signing by default starting May 2027.Read more ↗techrepublic com securityNews · Nov 11, 2026Microsoft Patches 1,235 Security Flaws: Outlook Zero-Day Already Under AttackA remote code execution vulnerability in Windows Remote Procedure Call Runtime caused by improper cryptographic signature verification. The November 2026 updates introduce related NTLM protections: Windows clients offer signing by default for authenticated connections, while servers initially continue accepting unsigned connections. Default server-side signing enforcement is planned for May 2027. Enhanced auditing supports identification of unsigned connections and compatibility issues during the transition; anonymous and guest sessions are exempt from signing requirements.Read more ↗security affairsNews · Nov 11, 2026Microsoft November Patch Tuesday: one exploited Outlook bug and 30 wormable flawsPatched RPC Runtime vulnerability included in the potentially wormable list. Individual technical details are not supplied, and the article qualifies the wormability assessment.Read more ↗csirt panamaNews · Nov 11, 2026CSIRT Panamá Aviso 2026-Nov-11 Actualizaciones de seguridad de Microsoft para Noviembre 2026. - CSIRT PanamáA critical remote code execution vulnerability in Remote Procedure Call Runtime addressed by Microsoft's November 2026 security updates.Read more ↗
+6 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.