CVE-2022-26809: Remote Code Execution in Windows RPC Runtime
- Vendor
- Microsoft Corporation
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.
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.
Exploits
2 exploits validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit.
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-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.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.