CVE-2022-35411: rpc.py through 0.6.0 allows Remote Code Execution because an unpickle occurs when the "serializer: pickle" HTT

Q: How do I fix CVE-2022-35411?

rpc.py: upgrade to newer than 0.6.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-35411 being exploited?

CVE-2022-35411 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-35411 affect?

CVE-2022-35411 affects rpc.py. Severity is critical (CVSS 9.8). 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 d

Q: How urgent is CVE-2022-35411?

Priority 69/100. Critical severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2022-35411 is a critical-severity flaw (CVSS 9.8) affecting rpc.py. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
EPSS top 1%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	46.6% (top 1%)
CISA exploited list	No
Weakness	CWE-522
Published	2022-07-08
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: rpc.py project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-07-08 19:15 UTCPublished CVE record published
2026-06-17 04:51 UTCUpdated Record last modified

rpc.py project rpc.py UPGRADE

Affected: >= 0.4.2 and <= 0.6.0

Fixed in: newer than 0.6.0

Safe to downgrade to: a release before 0.4.2

1. Check installed version

apt-cache policy rpc.py || rpm -q rpc.py || rpc.py --version

2. UPGRADE to newer than 0.6.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade rpc.py

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade rpc.py

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 0.4.2 (Debian / Ubuntu)

apt-cache madison rpc.py sudo apt install rpc.py=<VERSION_BEFORE_0.4.2> sudo apt-mark hold rpc.py

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list rpc.py sudo dnf downgrade rpc.py-<VERSION_BEFORE_0.4.2> sudo dnf versionlock add rpc.py

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

Python (pip) · rpc.py · NO FIX YET · vulnerable: >= 0.4.2, <= 0.6.0 · source

Fedora ELN · luksmeta · FIXED · 11-3.eln159 · FEDORA-2026-5176083b78 · source

sudo dnf upgrade --advisory=FEDORA-2026-5176083b78

Fedora 46 · openscad · FIXED · 2021.01-34.fc46 · FEDORA-2026-faf1721128 · source

sudo dnf upgrade --advisory=FEDORA-2026-faf1721128

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

GitHub PoC: CSpanias/rpc-rce.py (2 stars)
GitHub PoC: Neo-okami/CVE-2022-35411 (0 stars)
Write-up: medium.com/@elias.hohl/remote-code-execution-0-day-in-rpc-py-709c76690c30
GitHub PoC: fuzzlove/CVE-2022-35411
Exploit-DB: rpc.py 0.6.0 - Remote Code Execution (RCE)

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-35411?

rpc.py: upgrade to newer than 0.6.0. Exact commands for each OS are on this page.

Is CVE-2022-35411 being exploited?

CVE-2022-35411 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-35411 affect?

CVE-2022-35411 affects rpc.py. Severity is critical (CVSS 9.8). 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 d

How urgent is CVE-2022-35411?

Priority 69/100. Critical severity; EPSS top 1%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs