CVE-2020-22083: jsonpickle through 1.4.1 allows remote code execution during deserialization of a malicious payload through th

Q: How do I fix CVE-2020-22083?

jsonpickle: upgrade to newer than 1.4.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-22083 being exploited?

CVE-2020-22083 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-2020-22083 affect?

CVE-2020-22083 affects jsonpickle. Severity is critical (CVSS 9.8). jsonpickle through 1.4.1 allows remote code execution during deserialization of a malicious payload through the decode() function. Note: It has been argued that this is expected and clearly documented behaviour. pickle is known to be capabl

Q: How urgent is CVE-2020-22083?

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

This week

CRITICAL 9.8REMOTEUPGRADE

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

jsonpickle through 1.4.1 allows remote code execution during deserialization of a malicious payload through the decode() function. Note: It has been argued that this is expected and clearly documented behaviour. pickle is known to be capable of causing arbitrary code execution, and must not be used with un-trusted data

Why this priority

Critical severity
EPSS top 6%: 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	6.5% (top 6%)
CISA exploited list	No
Weakness	CWE-502
Published	2020-12-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: jsonpickle project

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

Am I affected?

Timeline

2020-12-17 16:15 UTCPublished CVE record published
2026-06-17 03:04 UTCUpdated Record last modified

jsonpickle project jsonpickle UPGRADE

Affected: <= 1.4.1

Fixed in: newer than 1.4.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jsonpickle || rpm -q jsonpickle || jsonpickle --version

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

sudo apt update && sudo apt install --only-upgrade jsonpickle

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jsonpickle

Note

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

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-2020-22083?

jsonpickle: upgrade to newer than 1.4.1. Exact commands for each OS are on this page.

Is CVE-2020-22083 being exploited?

CVE-2020-22083 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-2020-22083 affect?

CVE-2020-22083 affects jsonpickle. Severity is critical (CVSS 9.8). jsonpickle through 1.4.1 allows remote code execution during deserialization of a malicious payload through the decode() function. Note: It has been argued that this is expected and clearly documented behaviour. pickle is known to be capabl

How urgent is CVE-2020-22083?

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

References

← Back to latest CVEs