CVE-2022-35411

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 46%CVSS: 9.8Exploit: NoneExposed: 0

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

rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the "serializer: pickle" HTTP header is sent. In other words, although JSON (not Pickle) is the default data format, an unauthenticated client can cause the data to be processed with unpickle.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
67(Track*)
EG Risk 67/100SSVC: Track*

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%
Exploitation46% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
98.7%
KEV
Not listed

Published

July 8, 2022

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Jun 9, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

GitHub - ehtec/rpcpy-exploit: Unauthenticated Remote Code Execution for rpc.py server · GitHub

https://github.com/ehtec/rpcpy-exploit
github_commit

commit 491e7a841ed9 (abersheeran/rpc.py)

Fix landed in abersheeran/rpc.py commit 491e7a841ed9 — awaiting tagged release

https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
piprpc.py—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
rpc-py0.4.2, 0.4.3, 0.5.0, 0.5.1, 0.6.0——

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 37× 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-23 02:12 UTCEG score recompute
  2. 2026-07-22 22:59 UTCEG score recompute
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-20 17:05 UTCEPSS rescore
  8. 2026-07-19 14:29 UTCEPSS rescore
  9. 2026-07-18 10:03 UTCEPSS rescore
  10. 2026-07-18 10:03 UTCEPSS rescore
  11. 2026-07-17 02:54 UTCOSV refresh
  12. 2026-07-16 17:00 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 01:58 UTCEPSS rescore
  16. 2026-07-15 01:58 UTCEPSS rescore
  17. 2026-07-13 22:28 UTCEPSS rescore
  18. 2026-07-13 22:28 UTCEPSS rescore
  19. 2026-07-13 06:11 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-12 05:44 UTCEPSS rescore
  22. 2026-07-12 05:44 UTCEPSS rescore
  23. 2026-07-11 08:25 UTCEPSS rescore
  24. 2026-07-09 19:08 UTCEPSS rescore
  25. 2026-07-08 15:12 UTCEPSS rescore
Show 52 more
  1. 2026-07-04 06:29 UTCEPSS rescore
  2. 2026-07-04 06:29 UTCEPSS rescore
  3. 2026-07-01 15:04 UTCEPSS rescore
  4. 2026-06-29 01:02 UTCOSV refresh
  5. 2026-06-28 04:54 UTCEPSS rescore
  6. 2026-06-28 04:54 UTCEPSS rescore
  7. 2026-06-27 03:07 UTCEPSS rescore
  8. 2026-06-27 03:07 UTCEPSS rescore
  9. 2026-06-25 13:48 UTCEPSS rescore
  10. 2026-06-25 13:48 UTCEPSS rescore
  11. 2026-06-24 14:03 UTCEPSS rescore
  12. 2026-06-24 14:03 UTCEPSS rescore
  13. 2026-06-23 21:31 UTCEPSS rescore
  14. 2026-06-23 21:31 UTCEPSS rescore
  15. 2026-06-22 14:24 UTCEPSS rescore
  16. 2026-06-22 14:24 UTCEPSS rescore
  17. 2026-06-21 01:58 UTCEPSS rescore
  18. 2026-06-21 01:58 UTCEPSS rescore
  19. 2026-06-18 17:51 UTCEPSS rescore
  20. 2026-06-18 17:51 UTCEPSS rescore
  21. 2026-06-17 17:51 UTCEPSS rescore
  22. 2026-06-17 17:51 UTCEPSS rescore
  23. 2026-06-16 17:51 UTCEPSS rescore
  24. 2026-06-15 17:46 UTCEPSS rescore
  25. 2026-06-14 23:15 UTCEPSS rescore
  26. 2026-06-13 22:58 UTCEPSS rescore
  27. 2026-06-12 23:10 UTCEPSS rescore
  28. 2026-06-12 23:10 UTCEPSS rescore
  29. 2026-06-11 21:55 UTCOSV refresh
  30. 2026-06-11 13:58 UTCEPSS rescore
  31. 2026-06-11 13:58 UTCEPSS rescore
  32. 2026-06-10 22:17 UTCEPSS rescore
  33. 2026-06-08 14:15 UTCEPSS rescore
  34. 2026-06-08 14:15 UTCEPSS rescore
  35. 2026-06-05 22:46 UTCEPSS rescore
  36. 2026-06-05 22:45 UTCEPSS rescore
  37. 2026-06-05 06:09 UTCEPSS rescore
  38. 2026-06-05 06:09 UTCEPSS rescore
  39. 2026-06-04 13:11 UTCEPSS rescore
  40. 2026-06-04 13:11 UTCEPSS rescore
  41. 2026-06-01 13:50 UTCEPSS rescore
  42. 2026-06-01 13:50 UTCEPSS rescore
  43. 2026-05-31 00:15 UTCEPSS rescore
  44. 2026-05-31 00:15 UTCEPSS rescore
  45. 2026-05-29 13:43 UTCEPSS rescore
  46. 2026-05-29 13:43 UTCEPSS rescore
  47. 2026-05-27 13:39 UTCEPSS rescore
  48. 2026-05-27 13:39 UTCEPSS rescore
  49. 2026-05-26 13:43 UTCEPSS rescore
  50. 2026-05-26 13:43 UTCEPSS rescore
  51. 2026-05-25 19:19 UTCEG score recompute
  52. 2026-05-25 19:19 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCCSpanias/rpc-rce.py
    First seen Jul 28, 2025

    Exploit for CVE-2022-35411 — Unauthenticated RCE in rpc.py (<= 0.6.0)

    Open source ↗
  • Exploit-DBEDB-50983
    First seen Jul 29, 2022

    rpc.py 0.6.0 - Remote Code Execution (RCE)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-35411?
CVE-2022-35411 is a critical vulnerability published on July 8, 2022. rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the "serializer: pickle" HTTP header is sent. In other words, although JSON (not Pickle) is the default data format, an unauthenticated client can cause the data to be processed with unpickle.
When was CVE-2022-35411 disclosed?
CVE-2022-35411 was first published in the National Vulnerability Database on July 8, 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-35411 actively exploited?
CVE-2022-35411 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-35411?
CVE-2022-35411 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-35411?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-35411, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-35411

Explore →

Is Your Infrastructure Affected by CVE-2022-35411?

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

Start Free Scan →Browse All CVEs