CVE-2020-36216: An issue was discovered in Input<R> in the eventio crate before 0.5.1 for Rust
CVE-2020-36216 is a medium-severity flaw (CVSS 5.9) affecting eventio. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered in Input<R> in the eventio crate before 0.5.1 for Rust. Because a non-Send type can be sent to a different thread, a data race and memory corruption can occur.
Why this priority
- Public exploit reference
- Remotely exploitable, no login, no user action
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-36216?
eventio: upgrade to 0.5.1. Exact commands for each OS are on this page.
Is CVE-2020-36216 being exploited?
CVE-2020-36216 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-36216 affect?
CVE-2020-36216 affects eventio. Severity is medium (CVSS 5.9). An issue was discovered in Input<R> in the eventio crate before 0.5.1 for Rust. Because a non-Send type can be sent to a different thread, a data race and memory corruption can occur.
How urgent is CVE-2020-36216?
Priority 47/100. Public exploit reference; Remotely exploitable, no login, no user action