CVE-2022-26809
Remote Procedure Call Runtime Remote Code Execution Vulnerability
- CVSS
- 9.8Criticalscored by the publisher (CNA)
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 90.9%chance of exploitation in the next 30 daystop 0.2% of scored CVEsFIRST score of 11 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 15 Apr 2022analysed here 12 Nov 2026
Summary
Triage
- Exploitable
- At runtime
- Attack vector
- network
- Can a WAF block it?
- Partly. See why
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Microsoft Windows 10 Version 1507 | >= 10.0.10240.0 and < 10.0.10240.19265Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1607 | >= 10.0.14393.0 and < 10.0.14393.5066Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1809 | >= 10.0.17763.0 and < 10.0.17763.2803>= 10.0.0 and < 10.0.17763.2803Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 1909 | >= 10.0.0 and < 10.0.18363.2212Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 20H2 | >= 10.0.0 and < 10.0.19042.1645Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 21H1 | >= 10.0.0 and < 10.0.19043.1645Vendor says fixed in: not stated | |
| Microsoft Windows 10 Version 21H2 | >= 10.0.19043.0 and < 10.0.19044.1645Vendor says fixed in: not stated | |
| Microsoft Windows 11 version 21H2 | >= 10.0.0 and < 10.0.22000.613Vendor says fixed in: not stated | |
| Microsoft Windows 7 | >= 6.1.0 and < 6.1.7601.25924Vendor says fixed in: not stated | |
| Microsoft Windows 7 Service Pack 1 | >= 6.1.0 and < 6.1.7601.25924Vendor says fixed in: not stated | |
| Microsoft Windows 8.1 | >= 6.3.0 and < 6.3.9600.20337Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 R2 Service Pack 1 | >= 6.1.7601.0 and < 6.1.7601.25924Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) | >= 6.1.7601.0 and < 6.1.7601.25924Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 | >= 6.0.6003.0 and < 6.0.6003.21446Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 | >= 6.0.6003.0 and < 6.0.6003.21446Vendor says fixed in: not stated | |
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) | >= 6.0.6003.0 and < 6.0.6003.21446Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 | >= 6.2.9200.0 and < 6.2.9200.23679Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 R2 | >= 6.3.9600.0 and < 6.3.9600.20337Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 R2 (Server Core installation) | >= 6.3.9600.0 and < 6.3.9600.20337Vendor says fixed in: not stated | |
| Microsoft Windows Server 2012 (Server Core installation) | >= 6.2.9200.0 and < 6.2.9200.23679Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 | >= 10.0.14393.0 and < 10.0.14393.5066Vendor says fixed in: not stated | |
| Microsoft Windows Server 2016 (Server Core installation) | >= 10.0.14393.0 and < 10.0.14393.5066Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 | >= 10.0.17763.0 and < 10.0.17763.2803Vendor says fixed in: not stated | |
| Microsoft Windows Server 2019 (Server Core installation) | >= 10.0.17763.0 and < 10.0.17763.2803Vendor says fixed in: not stated | |
| Microsoft Windows Server 2022 | >= 10.0.20348.0 and < 10.0.20348.643Vendor says fixed in: not stated | |
| Microsoft Windows Server version 20H2 | >= 10.0.0 and < 10.0.19042.1645Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- 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
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 10 GitHub proofs of concept
- CISA SSVC
- exploitation poc, automatable yes, technical impact totalAssessed by CISA 20 Aug 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
- fuckjsonp/FuckJsonp-RCE-CVE-2022-26809-SQL-XSS-FuckJsonp409 stars
- s1ckb017/PoC-CVE-2022-26809108 stars
- yuanLink/CVE-2022-2680961 stars
- corelight/cve-2022-2680932 stars
and 6 more repositories
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 14 Apr 2022First proof-of-concept repository on GitHub (unvetted)
- 15 Apr 2022Published2 days later
- 20 Aug 2024CISA SSVC assessment: exploitation poc858 days (about 2 years) later
- 2 Jan 2025CVE record last updated135 days (about 5 months) later
- 12 Nov 2026Analysed by vulneraibility.com679 days (about 2 years) later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | HighComplete modification possible. | Complete modification possible. |
| Availability | HighFull outage possible. | Full outage possible. |
Common questions
Is CVE-2022-26809 being exploited?
Not confirmed. CVE-2022-26809 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 91% probability of exploitation in the next 30 days.
How severe is CVE-2022-26809?
CVE-2022-26809 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2022-26809?
Yes. A fix has been recorded for CVE-2022-26809. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2022-26809 affect?
CVE-2022-26809 affects microsoft:windows_10, microsoft:windows_11, microsoft:windows_7, microsoft:windows_8.1, and 6 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- msrc.microsoft.com /update-guide/vulnerability/CVE-2022-26809
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.