CVE-2020-24164: A deserialization flaw is present in Taoensso Nippy before 2.14.2
CVE-2020-24164 is a high-severity flaw (CVSS 7.8) affecting nippy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A deserialization flaw is present in Taoensso Nippy before 2.14.2. In some circumstances, it is possible for an attacker to create a malicious payload that, when deserialized, will allow arbitrary code to be executed. This occurs because there is automatic use of the Java Serializable interface.
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.8 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 1.1% (top 34%) |
| CISA exploited list | No |
| Weakness | CWE-502 |
| Published | 2020-09-11 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-24164?
nippy: upgrade to 2.14.2. Exact commands for each OS are on this page.
Is CVE-2020-24164 being exploited?
CVE-2020-24164 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-24164 affect?
CVE-2020-24164 affects nippy. Severity is high (CVSS 7.8). A deserialization flaw is present in Taoensso Nippy before 2.14.2. In some circumstances, it is possible for an attacker to create a malicious payload that, when deserialized, will allow arbitrary code to be executed. This occurs because th
How urgent is CVE-2020-24164?
Priority 44/100. High severity