rpc.py

Version	Released
`0.6.0` minor 1 CVE	Mar 31, 2022
`0.5.1` patch 1 CVE	Feb 18, 2022
`0.5.0` minor 1 CVE	Mar 05, 2021
`0.4.3` patch 1 CVE	Feb 14, 2021
`0.4.2` patch 1 CVE	Feb 11, 2021
`0.4.1` patch	Dec 03, 2020
`0.4.0` minor	Oct 17, 2020
`0.3.1` patch	Oct 03, 2020
`0.3.0` minor	Aug 09, 2020
`0.2.2` patch	Jul 20, 2020
`0.2.1` minor	Jul 18, 2020
`0.1.1` initial	Jul 16, 2020

0.6.0 minor

1 CVE

CVE-2022-35411 PYSEC-2026-526 GHSA-8rq8-f485-7v8x Jun 29, 2026

rpc.py vulnerable to Deserialization of Untrusted Data

9.8 / 10

Critical

Network Low None None Unchanged High High High

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 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]

Affected versions


          0.4.2


          0.4.3


          0.5.0


          0.5.1


          0.6.0

References

Updated Jul 01, 2026 · Source: OSV.dev

Mar 31, 2022

0.5.1 patch

1 CVE

CVE-2022-35411 PYSEC-2026-526 GHSA-8rq8-f485-7v8x Jun 29, 2026

rpc.py vulnerable to Deserialization of Untrusted Data

9.8 / 10

Critical

Network Low None None Unchanged High High High

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 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]

Affected versions


          0.4.2


          0.4.3


          0.5.0


          0.5.1


          0.6.0

References

Updated Jul 01, 2026 · Source: OSV.dev

Feb 18, 2022

0.5.0 minor

1 CVE

CVE-2022-35411 PYSEC-2026-526 GHSA-8rq8-f485-7v8x Jun 29, 2026

rpc.py vulnerable to Deserialization of Untrusted Data

9.8 / 10

Critical

Network Low None None Unchanged High High High

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 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]

Affected versions


          0.4.2


          0.4.3


          0.5.0


          0.5.1


          0.6.0

References

Updated Jul 01, 2026 · Source: OSV.dev

Mar 05, 2021

0.4.3 patch

1 CVE

CVE-2022-35411 PYSEC-2026-526 GHSA-8rq8-f485-7v8x Jun 29, 2026

rpc.py vulnerable to Deserialization of Untrusted Data

9.8 / 10

Critical

Network Low None None Unchanged High High High

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 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]

Affected versions


          0.4.2


          0.4.3


          0.5.0


          0.5.1


          0.6.0

References

Updated Jul 01, 2026 · Source: OSV.dev

Feb 14, 2021

0.4.2 patch

1 CVE

CVE-2022-35411 PYSEC-2026-526 GHSA-8rq8-f485-7v8x Jun 29, 2026

rpc.py vulnerable to Deserialization of Untrusted Data

9.8 / 10

Critical

Network Low None None Unchanged High High High

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 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]

Affected versions


          0.4.2


          0.4.3


          0.5.0


          0.5.1


          0.6.0

References

Updated Jul 01, 2026 · Source: OSV.dev

Feb 11, 2021

0.4.1 patch

Dec 03, 2020

0.4.0 minor

Oct 17, 2020

0.3.1 patch

Oct 03, 2020

0.3.0 minor

Aug 09, 2020

0.2.2 patch

Jul 20, 2020

0.2.1 minor

Jul 18, 2020

0.1.1 initial

Jul 16, 2020

Activity

Details