multiqueue Known Vulnerabilities & Fixes
multiqueue has 1 known security vulnerability in crates.io (Rust). Review the table below for affected and fixed versions. 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.
Is multiqueue in your project?
Check if you're affected by these 1 vulnerability.
Security Summary
- 1 affected version range has been identified across this advisory.
- 0% of known issue has a published fixed version.
- Remediation: cargo update -p multiqueue
Vulnerabilities
1 unique vulnerability — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details.
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2020-36463 Queues allow non-Send types to be sent to other threads, allowing data races | HIGH | All versions | No fix available |
About This Data
Vulnerability data for multiqueue 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 multiqueue.