slice-deque Known Vulnerabilities & Fixes
slice-deque has 3 known security vulnerabilities in crates.io (Rust). Upgrade to version 0.2.0 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 0.2.0
Upgrading to 0.2.0 or later resolves all 3 known vulnerabilities in slice-deque. Update Cargo.toml: slice-deque = "0.2.0"
Is slice-deque in your project?
Check if you're affected and upgrade to 0.2.0 to stay secure.
Security Summary
- 5 affected version ranges have been identified across these 3 advisories.
- 67% of known issues have a published fixed version.
- Remediation: cargo update -p slice-deque
Vulnerabilities
3 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed Aug 25, 2021, most recently Jul 16, 2025 (1421 days apart).
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2019-15543 Out of bounds write in slice-deque | CRITICAL | All versions | 0.2.0, 0.2.0 |
| CVE-2018-20995 Memory corruption slice-deque | CRITICAL | All versions | 0.1.16, 0.1.16 |
| GHSA-7mcq-f592-pf7v Slice Ring Buffer and Slice Deque contains four unique double-free vulnerabilities triggered through safe APIs | HIGH | All versions | No fix available |
About This Data
Vulnerability data for slice-deque is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related crates.io (Rust) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of slice-deque.