CVE-2020-36402: Solidity 0.7.5 has a stack-use-after-return issue in smtutil::CHCSmtLib2Interface::querySolver
CVE-2020-36402 is a high-severity flaw (CVSS 7.8) affecting solidity. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Solidity 0.7.5 has a stack-use-after-return issue in smtutil::CHCSmtLib2Interface::querySolver. NOTE: c39a5e2b7a3fabbf687f53a2823fc087be6c1a7e is cited in the OSV "fixed" field but does not have a code change.
Why this priority
- High severity
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.8 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 1.0% (top 39%) |
| CISA exploited list | No |
| Weakness | CWE-787 |
| Published | 2021-07-01 |
| 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-36402?
solidity: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2020-36402 being exploited?
CVE-2020-36402 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-36402 affect?
CVE-2020-36402 affects solidity. Severity is high (CVSS 7.8). Solidity 0.7.5 has a stack-use-after-return issue in smtutil::CHCSmtLib2Interface::querySolver. NOTE: c39a5e2b7a3fabbf687f53a2823fc087be6c1a7e is cited in the OSV "fixed" field but does not have a code change.
How urgent is CVE-2020-36402?
Priority 48/100. High severity; Public exploit reference
Related CVEs
- CVE-2022-33069 MEDIUM 5.5 DOWNGRADE Ethereum Solidity v0.8.14 contains an assertion failure via SMTEncoder::indexOrMemberAssignment() at SMTEncode