CVE-2020-20136: QuantConnect Lean versions from 2.3.0.0 to 2.4.0.1 are affected by an insecure deserialization vulnerability d
CVE-2020-20136 is a critical-severity flaw (CVSS 9.8) affecting lean. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
QuantConnect Lean versions from 2.3.0.0 to 2.4.0.1 are affected by an insecure deserialization vulnerability due to insecure configuration of TypeNameHandling property in Json.NET library.
Why this priority
- Critical severity
- 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 | 1.5% (top 25%) |
| CISA exploited list | No |
| Weakness | CWE-502 |
| Published | 2020-12-14 |
| 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-20136?
lean: upgrade to newer than 2.4.0.1. Exact commands for each OS are on this page.
Is CVE-2020-20136 being exploited?
CVE-2020-20136 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-20136 affect?
CVE-2020-20136 affects lean. Severity is critical (CVSS 9.8). QuantConnect Lean versions from 2.3.0.0 to 2.4.0.1 are affected by an insecure deserialization vulnerability due to insecure configuration of TypeNameHandling property in Json.NET library.
How urgent is CVE-2020-20136?
Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action