# CVE-2022-26809: Remote Procedure Call Runtime Remote Code Execution Vulnerability

> An attacker can execute arbitrary code on affected Windows systems by exploiting a vulnerability in the Remote Procedure Call Runtime.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2022
- **Updated:** 2 Jan 2025
- **Also known as:** GHSA-q2wc-9mx8-xr8j

## What is CVE-2022-26809?

CVE-2022-26809 is a critical code injection vulnerability in Microsoft Windows 10, published on 15 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Remote Procedure Call Runtime Remote Code Execution Vulnerability

## Which versions are affected by CVE-2022-26809?

It affects 10 products.


Products: Microsoft Windows 10, Microsoft Windows 11, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022.

## How do I fix CVE-2022-26809?

No fix has been published for CVE-2022-26809 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-26809 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-26809 exists.

Public exploit code:

- 警惕 一种针对红队的新型溯源手段! (github_poc): https://github.com/fuckjsonp/FuckJsonp-RCE-CVE-2022-26809-SQL-XSS-FuckJsonp
- PoC for CVE-2022-26809, analisys and considerations are shown in the github.io. (github_poc): https://github.com/s1ckb017/PoC-CVE-2022-26809
- https://github.com/yuanLink/CVE-2022-26809 (github_poc): https://github.com/yuanLink/CVE-2022-26809
- Detects attempts and successful exploitation of CVE-2022-26809 (github_poc): https://github.com/corelight/cve-2022-26809
- Remote Code Execution Exploit in the RPC Library (github_poc): https://github.com/websecnl/CVE-2022-26809
- The poc for CVE-2022-26809 RCE via RPC will be updated here.  (github_poc): https://github.com/sherlocksecurity/Microsoft-CVE-2022-26809-The-Little-Boy

## Other vulnerabilities in Microsoft Windows 10

- [CVE-2015-2426](https://insights.sbomify.com/CVE-2015-2426/): Microsoft Windows Adobe Type Manager Library Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2015-1769](https://insights.sbomify.com/CVE-2015-1769/): Microsoft Windows Mount Manager Privilege Escalation (medium 6.6, exploited in the wild)
- [CVE-2020-1467](https://insights.sbomify.com/CVE-2020-1467/): Windows Hard Link Elevation of Privilege Vulnerability (critical 10.0)
- [CVE-2021-26424](https://insights.sbomify.com/CVE-2021-26424/): Windows TCP/IP Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2021-28476](https://insights.sbomify.com/CVE-2021-28476/): Windows Hyper-V Remote Code Execution Vulnerability (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26809 and fix it if it is affected.

What it is: CVE-2022-26809 is a critical code injection vulnerability in Microsoft Windows 10, published on 15 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-26809 exists.

Affected product: Microsoft Windows 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-26809/ (Markdown: https://insights.sbomify.com/CVE-2022-26809/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-26809
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-26809
- OSV: https://osv.dev/vulnerability/CVE-2022-26809

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-26809/
Summaries are generated and may contain mistakes; the official description above is the record.