Remote Procedure Call Runtime Remote Code Execution Vulnerability
CVE-2022-26809
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-04-16. NVD baseline CVSS 9.8; sources differ by 0.0.
- High exploitation likelihood — EPSS 91%
- Public exploit code is available (ssvc poc, epss top5pct, epss high, public exploit)
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 9.8CRITICALmedium confidence
- EG Risk
- 95EG Risk 95/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation91% × 40%Automatability100% × 15%CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 91%
- EPSS %ILE
- 99th
- KEV
- Not listed
CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
April 15, 2022
Last Modified
November 21, 2024
Advisory Details (1)
Auto-updated Oct 3, 2026Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-26809Vendor Advisories for CVE-2022-26809(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Data Freshness Timeline
(refreshed 2× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-30 15:52 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescore
- 2026-09-24 14:00 UTCEPSS rescore
- 2026-09-23 13:45 UTCEPSS rescore
- 2026-09-11 09:33 UTCEPSS rescore
- 2026-09-07 15:58 UTCEPSS rescore
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-08-30 19:14 UTCEPSS rescore
- 2026-08-28 21:38 UTCEPSS rescore
- 2026-08-24 14:13 UTCEPSS rescore
- 2026-08-15 01:27 UTCEPSS rescore
- 2026-08-12 13:48 UTCEPSS rescore
- 2026-08-08 16:34 UTCEPSS rescore
- 2026-08-07 16:24 UTCEPSS rescore
- 2026-08-06 13:44 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-07-30 16:25 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 02:09 UTCEG score recompute
- 2026-07-22 22:56 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
Show 24 moreShow fewer
- 2026-07-07 13:44 UTCEPSS rescore
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
- 2026-07-01 15:04 UTCEPSS rescore
- 2026-06-27 03:07 UTCEPSS rescore
- 2026-06-23 21:31 UTCEPSS rescore
- 2026-06-23 21:31 UTCEPSS rescore
- 2026-06-18 17:51 UTCEPSS rescore
- 2026-06-18 17:51 UTCEPSS rescore
- 2026-06-16 17:51 UTCEPSS rescore
- 2026-06-15 17:46 UTCEPSS rescore
- 2026-06-12 23:10 UTCEPSS rescore
- 2026-06-12 23:10 UTCEPSS rescore
- 2026-06-06 13:46 UTCEPSS rescore
- 2026-06-06 13:46 UTCEPSS rescore
- 2026-06-05 06:09 UTCEPSS rescore
- 2026-06-05 06:09 UTCEPSS rescore
- 2026-05-29 13:42 UTCEPSS rescore
- 2026-05-26 13:43 UTCEPSS rescore
- 2026-05-25 23:38 UTCEG score recompute
- 2026-05-25 23:38 UTCVendor advisory
- 2026-05-25 23:38 UTCGHSA enrichment
Publicly available exploits
(7 references)Working exploit code is in the public domain (7 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCfuckjsonp/FuckJsonp-RCE-CVE-2022-26809-SQL-XSS-FuckJsonpFirst seen Jul 27, 2022
警惕 一种针对红队的新型溯源手段!
Open source ↗ - GitHub PoCs1ckb017/PoC-CVE-2022-26809First seen Jun 13, 2022
PoC for CVE-2022-26809, analisys and considerations are shown in the github.io.
Open source ↗ - Open source ↗GitHub PoCyuanLink/CVE-2022-26809First seen May 1, 2022
- Open source ↗GitHub PoCauduongxuan/CVE-2022-26809First seen Apr 14, 2022
- GitHub PoCcorelight/cve-2022-26809First seen Apr 14, 2022
Detects attempts and successful exploitation of CVE-2022-26809
Open source ↗ - GitHub PoCsherlocksecurity/Microsoft-CVE-2022-26809-The-Little-BoyFirst seen Apr 14, 2022
The poc for CVE-2022-26809 RCE via RPC will be updated here.
Open source ↗ - GitHub PoCwebsecnl/CVE-2022-26809First seen Apr 14, 2022
Remote Code Execution Exploit in the RPC Library
Open source ↗
Frequently asked(5)
What is CVE-2022-26809?
When was CVE-2022-26809 disclosed?
Is CVE-2022-26809 actively exploited?
What is the CVSS score of CVE-2022-26809?
How do I remediate CVE-2022-26809?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2022-26809
Is Your Infrastructure Affected by CVE-2022-26809?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.