CVE-2020-36440: An issue was discovered in the libsbc crate before 0.1.5 for Rust
CVE-2020-36440 is a high-severity flaw (CVSS 8.1) affecting libsbc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered in the libsbc crate before 0.1.5 for Rust. For Decoder<R>, it implements Send for any R: Read.
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-36440?
libsbc: upgrade to 0.1.5. Exact commands for each OS are on this page.
Is CVE-2020-36440 being exploited?
CVE-2020-36440 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-36440 affect?
CVE-2020-36440 affects libsbc. Severity is high (CVSS 8.1). An issue was discovered in the libsbc crate before 0.1.5 for Rust. For Decoder<R>, it implements Send for any R: Read.
How urgent is CVE-2020-36440?
Priority 47/100. High severity; Remotely exploitable, no login, no user action