Description
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.
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.
Exploit-DB 1
- rpc.py 0.6.0 - Remote Code Execution (RCE) EDB-50983 · remote · Jul 29, 2022
GitHub 2 repositories
-
CSpanias/rpc-rce.py ★ 2 · Jul 28, 2025
Exploit for CVE-2022-35411 — Unauthenticated RCE in rpc.py (<= 0.6.0)
-
Neo-okami/CVE-2022-35411 ★ 0 · Jul 16, 2025
rpc.py 0.6.0 - Remote Code Execution (RCE)
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| PyPI | rpc-py | >= 0.4.2, <= 0.6.0 | — | GHSA-8rq8-f485-7v8x |