https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 16 Oct 2026 12:28:25 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-18254 EUVD-2026-18254 https://cve.radiocsirt.org/vuln/euvd-2026-18254 https://cve.radiocsirt.org/vuln/fkie_cve-2022-35411 <p>rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the &#34;serializer: pickle&#34; 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.</p> <p>rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the &#34;serializer: pickle&#34; 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-35411 https://cve.radiocsirt.org/vuln/ghsa-8rq8-f485-7v8x <p><strong>Affected:</strong> PyPI: rpc.py</p> <p>rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the &#34;serializer: pickle&#34; 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.</p> <p>[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.</p> <p>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]</p> <p><strong>Affected:</strong> PyPI: rpc.py</p> <p>rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the &#34;serializer: pickle&#34; 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.</p> <p>[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.</p> <p>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]</p> https://cve.radiocsirt.org/vuln/ghsa-8rq8-f485-7v8x https://cve.radiocsirt.org/vuln/gsd-2022-35411 gsd-2022-35411 https://cve.radiocsirt.org/vuln/gsd-2022-35411 https://cve.radiocsirt.org/vuln/pysec-2026-526 <p><strong>Affected:</strong> PyPI: rpc-py</p> <p>rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the &#34;serializer: pickle&#34; 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.</p> <p>[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.</p> <p>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]</p> <p><strong>Affected:</strong> PyPI: rpc-py</p> <p>rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the &#34;serializer: pickle&#34; 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.</p> <p>[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.</p> <p>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]</p> https://cve.radiocsirt.org/vuln/pysec-2026-526