CVE-2020-36215: An issue was discovered in the hashconsing crate before 1.1.0 for Rust

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

hashconsing: upgrade to 1.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-36215 being exploited?

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

CVE-2020-36215 affects hashconsing. Severity is high (CVSS 7.5). An issue was discovered in the hashconsing crate before 1.1.0 for Rust. Because HConsed does not have bounds on its Send trait or Sync trait, memory corruption can occur.

Q: How urgent is CVE-2020-36215?

Priority 54/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2020-36215 is a high-severity flaw (CVSS 7.5) affecting hashconsing. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in the hashconsing crate before 1.1.0 for Rust. Because HConsed does not have bounds on its Send trait or Sync trait, memory corruption can occur.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.4% (top 28%)
CISA exploited list	No
Weakness	CWE-662, CWE-787
Published	2021-01-26
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: hashconsing project

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

Am I affected?

Timeline

2021-01-26 18:15 UTCPublished CVE record published
2026-06-17 03:15 UTCUpdated Record last modified

hashconsing project hashconsing UPGRADE

Affected: < 1.1.0

Fixed in: 1.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 1.1.0 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade hashconsing

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-36215?

hashconsing: upgrade to 1.1.0. Exact commands for each OS are on this page.

Is CVE-2020-36215 being exploited?

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

CVE-2020-36215 affects hashconsing. Severity is high (CVSS 7.5). An issue was discovered in the hashconsing crate before 1.1.0 for Rust. Because HConsed does not have bounds on its Send trait or Sync trait, memory corruption can occur.

How urgent is CVE-2020-36215?

Priority 54/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs