CVE-2022-26809

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-04-16. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 91%
CISA-KEV: Not listedEPSS: 91%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Remote Procedure Call Runtime Remote Code Execution Vulnerability

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
96(Attend)
EG Risk 96/100SSVC: Attend

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 computed
Severity98% × 45%
Exploitation91% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
99.8%
KEV
Not listed

Published

April 15, 2022

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated May 26, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security 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-26809

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 14× 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.

  1. 2026-07-24 14:15 UTCEPSS rescore
  2. 2026-07-23 02:09 UTCEG score recompute
  3. 2026-07-22 22:56 UTCEG score recompute
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-22 14:06 UTCEPSS rescore
  6. 2026-07-15 16:56 UTCEPSS rescore
  7. 2026-07-15 16:56 UTCEPSS rescore
  8. 2026-07-07 13:44 UTCEPSS rescore
  9. 2026-07-06 16:25 UTCEPSS rescore
  10. 2026-07-06 16:25 UTCEPSS rescore
  11. 2026-07-04 06:29 UTCEPSS rescore
  12. 2026-07-04 06:29 UTCEPSS rescore
  13. 2026-07-01 15:04 UTCEPSS rescore
  14. 2026-06-27 03:07 UTCEPSS rescore
  15. 2026-06-23 21:31 UTCEPSS rescore
  16. 2026-06-23 21:31 UTCEPSS rescore
  17. 2026-06-18 17:51 UTCEPSS rescore
  18. 2026-06-18 17:51 UTCEPSS rescore
  19. 2026-06-16 17:51 UTCEPSS rescore
  20. 2026-06-15 17:46 UTCEPSS rescore
  21. 2026-06-12 23:10 UTCEPSS rescore
  22. 2026-06-12 23:10 UTCEPSS rescore
  23. 2026-06-06 13:46 UTCEPSS rescore
  24. 2026-06-06 13:46 UTCEPSS rescore
  25. 2026-06-05 06:09 UTCEPSS rescore
Show 6 more
  1. 2026-06-05 06:09 UTCEPSS rescore
  2. 2026-05-29 13:42 UTCEPSS rescore
  3. 2026-05-26 13:43 UTCEPSS rescore
  4. 2026-05-25 23:38 UTCEG score recompute
  5. 2026-05-25 23:38 UTCVendor advisory
  6. 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-FuckJsonp
    First seen Jul 27, 2022

    警惕 一种针对红队的新型溯源手段!

    Open source ↗
  • GitHub PoCs1ckb017/PoC-CVE-2022-26809
    First seen Jun 13, 2022

    PoC for CVE-2022-26809, analisys and considerations are shown in the github.io.

    Open source ↗
  • GitHub PoCyuanLink/CVE-2022-26809
    First seen May 1, 2022
    Open source ↗
  • GitHub PoCcorelight/cve-2022-26809
    First seen Apr 14, 2022

    Detects attempts and successful exploitation of CVE-2022-26809

    Open source ↗
  • GitHub PoCwebsecnl/CVE-2022-26809
    First seen Apr 14, 2022

    Remote Code Execution Exploit in the RPC Library

    Open source ↗
  • GitHub PoCsherlocksecurity/Microsoft-CVE-2022-26809-The-Little-Boy
    First seen Apr 14, 2022

    The poc for CVE-2022-26809 RCE via RPC will be updated here.

    Open source ↗
  • GitHub PoCauduongxuan/CVE-2022-26809
    First seen Apr 14, 2022
    Open source ↗

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-26809?
CVE-2022-26809 is a critical vulnerability published on April 15, 2022. Remote Procedure Call Runtime Remote Code Execution Vulnerability
When was CVE-2022-26809 disclosed?
CVE-2022-26809 was first published in the National Vulnerability Database on April 15, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-26809 actively exploited?
CVE-2022-26809 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-26809?
CVE-2022-26809 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-26809?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-26809, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-26809

Explore →

Is Your Infrastructure Affected by CVE-2022-26809?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs