PatchTheCVECVE-2020-36439: An issue was discovered in the ticketed_lock crate before 0.3.0 for Rust
CVE-2020-36439 is a high-severity flaw (CVSS 8.1) affecting ticketed lock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered in the ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket<T> and WriteTicket<T>.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.1 (High) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.8% (top 45%) |
| CISA exploited list | No |
| Weakness | CWE-362 |
| Published | 2021-08-08 |
| Last modified | 2026-06-17 |
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-36439?
ticketed lock: upgrade to 0.3.0. Exact commands for each OS are on this page.
Is CVE-2020-36439 being exploited?
CVE-2020-36439 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-36439 affect?
CVE-2020-36439 affects ticketed lock. Severity is high (CVSS 8.1). An issue was discovered in the ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket<T> and WriteTicket<T>.
How urgent is CVE-2020-36439?
Priority 47/100. High severity; Remotely exploitable, no login, no user action