CVE-2020-36208: An issue was discovered in the conquer-once crate before 0.3.2 for Rust
CVE-2020-36208 is a high-severity flaw (CVSS 7.8) affecting conquer-once. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered in the conquer-once crate before 0.3.2 for Rust. Thread crossing can occur for a non-Send but Sync type, leading to memory corruption.
Why this priority
- High severity
- Public exploit reference
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-36208?
conquer-once: upgrade to 0.3.2. Exact commands for each OS are on this page.
Is CVE-2020-36208 being exploited?
CVE-2020-36208 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-36208 affect?
CVE-2020-36208 affects conquer-once. Severity is high (CVSS 7.8). An issue was discovered in the conquer-once crate before 0.3.2 for Rust. Thread crossing can occur for a non-Send but Sync type, leading to memory corruption.
How urgent is CVE-2020-36208?
Priority 42/100. High severity; Public exploit reference