CVE-2020-36207: An issue was discovered in the aovec crate through 2020-12-10 for Rust
CVE-2020-36207 is a high-severity flaw (CVSS 7.0) affecting aovec. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- High severity
A fixed release or distro patch exists.
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-36207?
aovec: upgrade to newer than 2020-12-10. Exact commands for each OS are on this page.
Is CVE-2020-36207 being exploited?
CVE-2020-36207 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-36207 affect?
CVE-2020-36207 affects aovec. Severity is high (CVSS 7.0). 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.
How urgent is CVE-2020-36207?
Priority 30/100. High severity