CVE-2020-36207

HIGHNVD 7.07.0—

7.0

An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.

CVSS v3: 7.0
EG Score: 7.0(medium)
EPSS: 21.0%
KEV: Not listed

Published

January 26, 2021

Last Modified

November 21, 2024

References (2)

cve@mitrehttps://rustsec.org/advisories/RUSTSEC-2020-0099.html
af854a3a-2127-422b-91ae-364da2661108https://rustsec.org/advisories/RUSTSEC-2020-0099.html

Patch Availability(1)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
rust	aovec	—	ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)

crates.io(1)

Package	Vulnerable range	Fixed in	Dependents
aovec	—	—	—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 16× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 21:40 UTCEG score recompute
2026-05-26 21:40 UTCGHSA enrichment
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2020-36207?

CVE-2020-36207 is a high vulnerability published on January 26, 2021. An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec<T> does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.

When was CVE-2020-36207 disclosed?

CVE-2020-36207 was first published in the National Vulnerability Database on January 26, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-36207 actively exploited?

CVE-2020-36207 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-36207?

CVE-2020-36207 has a CVSS v3 base score of 7.0 (NVD).

How do I remediate CVE-2020-36207?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-36207, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-36207

Explore →

Is Your Infrastructure Affected by CVE-2020-36207?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-36207

📅 Published

🔄 Last Modified

🔗 References (2)