Vulnerability in Rpc.py Project
CVE-2022-35411
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.466, 98.8th percentile (last changed ); up from 0.457 30 days earlier. About EPSS.
EPSS over last 30 days · oldest: 0.457 · newest: 0.466 · change: +0.009
Affected products
Weakness classification (CWE)
Public exploits and proof-of-concept code
3 public repositories with exploit or proof-of-concept code for this CVE:
- CSpanias/rpc-rce.py (2 stars, last pushed 2025-07-28): Exploit for CVE-2022-35411 — Unauthenticated RCE in rpc.py (<= 0.6.0)
- Neo-okami/CVE-2022-35411 (last pushed 2024-04-25): rpc.py 0.6.0 - Remote Code Execution (RCE)
- fuzzlove/CVE-2022-35411
Also mentioned in 8 other repositories (ARPSyndicate/cvemon, ARPSyndicate/cve-scores, battleofthebots/system-gateway, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30 (Exploit)
- github.com/ehtec/rpcpy-exploit (Exploit, Third Party Advisory)
- github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd (Patch, Third Party Advisory)
- packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html (Exploit, VDB Entry, Third Party Advisory)
This CVE has public exploit evidence. See the latest CVEs with public exploits.