https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-16T14:22:15.400967+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-18254 EUVD-2026-18254 2026-10-16T14:22:15.493219+00:00 EUVD-2026-18254 https://cve.radiocsirt.org/vuln/fkie_cve-2022-35411 fkie_cve-2022-35411 2026-10-16T14:22:15.493263+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-8rq8-f485-7v8x GHSA-8rq8-f485-7v8x — rpc.py vulnerable to Deserialization of Untrusted Data 2026-10-16T14:22:15.493310+00:00

Affected: PyPI: rpc.py

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](https://github.com/abersheeran/rpc.py/issues/22), 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](https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd) exists on the `master` branch. As a workaround, use the following code to turn off pickle in older versions: ``` del SERIALIZER_NAMES[PickleSerializer.name] del SERIALIZER_TYPES[PickleSerializer.content_type]

 https://cve.radiocsirt.org/vuln/gsd-2022-35411 gsd-2022-35411 2026-10-16T14:22:15.493362+00:00 gsd-2022-35411 https://cve.radiocsirt.org/vuln/pysec-2026-526 PYSEC-2026-526 — rpc.py vulnerable to Deserialization of Untrusted Data 2026-10-16T14:22:15.493382+00:00

Affected: PyPI: rpc-py

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](https://github.com/abersheeran/rpc.py/issues/22), 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](https://github.com/abersheeran/rpc.py/commit/491e7a841ed9a754796d6ab047a9fb16e23bf8bd) exists on the `master` branch. As a workaround, use the following code to turn off pickle in older versions: ``` del SERIALIZER_NAMES[PickleSerializer.name] del SERIALIZER_TYPES[PickleSerializer.content_type]