CVE-2022-35411Rpc.py Insecure Deserialization
rpc.py vulnerable to Deserialization of Untrusted Data
Published Jul 9, 2022 · Updated Aug 12, 2026 · Also known as GHSA-8rq8-f485-7v8x, PYSEC-2026-526
Key Facts
Patch immediately- CVE-2022-35411 is a critical-severity vulnerability (CVSS 9.8 v3.1) affecting Rpc.py (Rpc.py Project), rpc-py (pypi).
- It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
- EPSS estimates a 46% probability of exploitation in the next 30 days.
- Fixed versions are available, including Rpc.py <=0.6.0, Rpc.py 0.6.0.
- Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.
Scores
CVSS v3.1
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
46%
Higher than 98.7% of all scored CVEs
Exploit maturity
Proof of concept
ATLAS score
46/100
Publication score, see How it works
Exploitation Verdict
KEV listed
Not listed
Federal due date
None
No federal due date
Ransomware use
Not reported
Attributed actors
None named
Exploit & Defence Guidance
Exploit maturity
Proof of concept
Public exploit code
1
Proof-of-concept links
In-the-wild evidence
0
Reports of active use
Advisories And Exploit References
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.
Affected Products
3 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Rpc.pyRpc.py Project | >= 0.4.2 | 0.6.0 |
| rpc-pypypi | >= 0.4.2 | n/a |
Patched Releases
Rpc.py
<=0.6.0
Timeline
Publicly disclosed
Jul 9, 2022
Last updated
Aug 12, 2026
Weakness Type
- CWE-502 Deserialization of Untrusted Data
- CWE-522 Insufficiently Protected Credentials
References
- advisorycve.org · CVERecord
- advisorynvd.nist.gov · CVE-2022-35411
- advisoryGHSA advisory
- exploitExploitDB-50983
- articlepacketstormsecurity.com · rpc.py-0.6.0-Remote-Code-Execution.html
FAQ
Common Questions.
rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the "serializer: pickle" HTTP header is sent.
Affected: Rpc.py (Rpc.py Project) versions >= 0.4.2; rpc-py (pypi) versions >= 0.4.2. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
Fixed versions are available, including Rpc.py <=0.6.0, Rpc.py 0.6.0.
Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.
Is CVE-2022-35411 On Your Attack Surface?
Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.
Request A Demo