PYSEC-2026-526
See a problem?- Import Source
- https://github.com/pypa/advisory-database/blob/main/vulns/rpc-py/PYSEC-2026-526.yaml
- JSON Data
- https://api.osv.dev/v1/vulns/PYSEC-2026-526
- Aliases
- Published
- 2026-06-29T11:50:33.689769Z
- Modified
- 2026-07-01T20:23:04.195521Z
- Severity
-
- 9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- rpc.py vulnerable to Deserialization of Untrusted Data
- Details
-
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.
Per the maintainer, rpc.py is not designed for an API that is open to the outside world, and external requests cannot reach rpc.py in real world use.
A fix exists on the
masterbranch. As a workaround, use the following code to turn off pickle in older versions: ``` del SERIALIZERNAMES[PickleSerializer.name] del SERIALIZERTYPES[PickleSerializer.content_type] - References
-
- https://nvd.nist.gov/vuln/detail/CVE-2022-35411
- https://github.com/abersheeran/rpc.py/issues/22
- https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd
- https://github.com/abersheeran/rpc.py
- https://github.com/ehtec/rpcpy-exploit
- https://medium.com/%40elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30
- https://medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30
- http://packetstormsecurity.com/files/167872/rpc.py-0.6.0-Remote-Code-Execution.html
- https://pypi.org/project/rpc-py
- https://github.com/advisories/GHSA-8rq8-f485-7v8x
Affected packages
PyPI / rpc-py
Package
- Name
- rpc-py
- View open source insights on deps.dev
- Purl
- pkg:pypi/rpc-py