Skip to main content
Mallory
HighVulnerability

CVE-2026-62781: Microsoft RPC Runtime Library Remote Code Execution Vulnerability

Published Aug 11, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.1High · v3.1
EPSS0.71%54th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-62781CWE-122 · Heap-based Buffer Overflow

CVE-2026-62781 is a high-severity remote code execution vulnerability in the Microsoft RPC Runtime Library. The flaw is caused by a heap-based buffer overflow in RPC Runtime processing, allowing memory corruption during handling of network-reachable RPC traffic. An unauthenticated attacker can exploit the vulnerability over a network, and successful exploitation may result in arbitrary code execution in the context of the targeted service or system. The issue affects multiple supported Microsoft Windows client and server releases, including Windows 10, Windows 11, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022, and Windows Server 2025.

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 can allow an unauthenticated remote attacker to execute arbitrary code on a vulnerable Windows system over the network. Because the vulnerability is in the RPC Runtime Library, compromise could lead to full system compromise depending on the privileges of the affected RPC service, including loss of confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

No specific vendor workaround or mitigation is available in the provided information. Until patches are fully deployed, reduce exposure of vulnerable systems by limiting network access to RPC services through segmentation and access controls, and prioritize patching of internet-exposed and high-value systems.

Remediation

Patch, then assume compromise.

Apply the Microsoft security updates released for CVE-2026-62781 to all affected Windows client and server systems. Upgrade affected installations to the fixed builds identified by Microsoft for each supported release and ensure patch deployment covers all exposed and internally reachable systems running vulnerable RPC Runtime components.

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 Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
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-62781 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-62781 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-62781?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-62781.
Is there a patch for CVE-2026-62781?
Apply the Microsoft security updates released for CVE-2026-62781 to all affected Windows client and server systems. Upgrade affected installations to the fixed builds identified by Microsoft for each supported release and ensure patch deployment covers all exposed and internally reachable systems running vulnerable RPC Runtime components.
What products are affected by CVE-2026-62781?
Microsoft Corporation Windows Server 2012, Microsoft Corporation Windows Server 2012 R2, Microsoft Corporation Windows Server 2016, Microsoft Corporation Windows Server 2019, Microsoft Corporation Windows Server 2022, and 9 more.
How severe is CVE-2026-62781?
CVE-2026-62781 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.71% (54th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

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

View more in app →
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 activity1Community discussion across Reddit, Mastodon, and other social sources.