PatchTheCVECVE-2020-35895: An issue was discovered in the stack crate before 0.3.1 for Rust
CVE-2020-35895 is a critical-severity flaw (CVSS 9.8) affecting stack. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered in the stack crate before 0.3.1 for Rust. ArrayVec has an out-of-bounds write via element insertion.
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.9% (top 21%) |
| CISA exploited list | No |
| Weakness | CWE-787 |
| Published | 2020-12-31 |
| 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-35895?
stack: upgrade to 0.3.1. Exact commands for each OS are on this page.
Is CVE-2020-35895 being exploited?
CVE-2020-35895 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-35895 affect?
CVE-2020-35895 affects stack. Severity is critical (CVSS 9.8). An issue was discovered in the stack crate before 0.3.1 for Rust. ArrayVec has an out-of-bounds write via element insertion.
How urgent is CVE-2020-35895?
Priority 59/100. Critical severity; Remotely exploitable, no login, no user action