Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2022-26809: Remote Code Execution in Windows RPC Runtime

Published Apr 15, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS90.9%100th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2022-26809CWE-190

CVE-2022-26809 is a critical remote code execution vulnerability in the Windows Remote Procedure Call (RPC) Runtime, associated with the rpcrt4.dll library. Available technical analysis indicates the flaw involves an integer overflow in RPC packet-processing logic that can lead to a subsequent heap buffer overflow. Referenced vulnerable code paths include RPC response and buffer coalescing routines such as OSF_CCALL::ProcessResponse, OSF_CCALL::ProcessResponsePDU, OSF_SCALL::GetCoalescedBuffer, and OSF_CCALL::GetCoalescedBuffer. Because the vulnerable routines are present in RPC processing on both client and server sides, a specially crafted RPC message can trigger memory corruption in the context of the RPC process. The vulnerability has been described as zero-click and unauthenticated under exposed conditions.

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 result in unauthenticated remote code execution on vulnerable Windows systems. Because the flaw is in core RPC runtime processing, exploitation may allow arbitrary code execution in the context of the affected RPC-handling process without user interaction. The vulnerability is considered critical and was reported with a CVSS score of 9.8.

Mitigation

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

If immediate patching is not possible, reduce exposure of RPC services from untrusted networks and strictly limit inbound access to systems that require the service. Historical guidance referenced restricting external access to TCP port 445 and limiting inbound connections to only necessary hosts such as domain controllers and file or print servers, but later Microsoft guidance indicated port blocking alone does not protect against all attack scenarios. Network segmentation and minimizing unnecessary RPC exposure can reduce risk, but they are not complete substitutes for patching.

Remediation

Patch, then assume compromise.

Apply the Microsoft April 2022 security updates that address CVE-2022-26809 across affected Windows versions. Patch validation may require confirming installation of the relevant cumulative or rollup update for the specific Windows release rather than relying solely on individual hotfix identifiers, because monthly rollups may supersede earlier KBs. Patching is the primary and recommended remediation.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2022-26809This repository contains a collection of proof-of-concept (PoC) exploits and research tools for Windows DCE/RPC vulnerabilities, specifically CVE-2022-26809 and CVE-2021-36942 (PetitPotam). The main exploit, 'PetitPotam/petitpotam.py', is a Python script that coerces NTLM authentication from Windows hosts by abusing EFS-RPC methods over named pipes (such as 'lsarpc'). The exploit can force a Windows system to authenticate to an attacker-controlled SMB server, enabling credential capture or relay attacks. The repository also includes a fake SMB server implementation ('attacker-server/fake_smb_server.py'), a custom RPC implementation ('attacker-server/rpcrt.py'), and a C-based RPC demo ('pipedemo' directory) for further research and testing. The PoC demonstrates network-based attack vectors, requiring the attacker to be able to communicate with the target over the network (typically TCP port 445 or a custom RPC port). The exploit is not weaponized but provides a working proof-of-concept for security research and red teaming. The repository targets unpatched Microsoft Windows systems vulnerable to the specified CVEs.yuanLink · Disclosed May 1, 2022 · python · c · networkPoCPoC-CVE-2022-26809This repository contains a single Python proof-of-concept exploit (PoC_CVE_2022_26809.py) and a README. The exploit targets CVE-2022-26809, a critical integer overflow vulnerability in Microsoft Windows RPC over SMB named pipes. The PoC is written in Python and leverages the Impacket library, with custom overrides to manipulate packet fragmentation and trigger the vulnerability. The exploit works by sending a very large number of crafted RPC fragments to the target's SMB named pipe endpoint, aiming to overflow a 32-bit integer and cause a heap buffer overflow in the RPC service. The README provides context, limitations, and references to vulnerable/patched server code. The exploit is a proof-of-concept and is not fully weaponized; it is intended for research and learning about RPC internals and the vulnerability. No hardcoded endpoints are present; the target IP and named pipe are provided as arguments at runtime.s1ckb017 · Disclosed Jun 13, 2022 · python · networkPoC
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 10operating_system
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 1909operating_system
Microsoft CorporationWindows 10 20h2operating_system
Microsoft CorporationWindows 10 21h1operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 11operating_system
Microsoft CorporationWindows 11 21h2operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_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 20h2operating_system
FAQ

Frequently asked questions

Is CVE-2022-26809 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2022-26809?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2022-26809, the earliest disclosed May 1, 2022.
Is there a patch for CVE-2022-26809?
Apply the Microsoft April 2022 security updates that address CVE-2022-26809 across affected Windows versions. Patch validation may require confirming installation of the relevant cumulative or rollup update for the specific Windows release rather than relying solely on individual hotfix identifiers, because monthly rollups may supersede earlier KBs.
What products are affected by CVE-2022-26809?
Microsoft Corporation Windows 10, Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 1909, and at least 17 more.
How severe is CVE-2022-26809?
CVE-2022-26809 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 90.9% (100th percentile) as of Oct 16, 2026.
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 malware1Malware 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 activityCommunity discussion across Reddit, Mastodon, and other social sources.