Read the docs
TI-2020-18534 Aliases CVE-2020-36214GHSA-jphw-p3m6-pj3c

An issue was discovered in the multiqueue2 crate before 0.1.7 for Rust.

Priority LOW 29CWE-662Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
None · None · High
Fix status
Fixed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub.

Summary

An issue was discovered in the multiqueue2 crate before 0.1.7 for Rust. Because a non-Send type can be sent to a different thread, a data race can occur.

Why it matters now

EPSS 0.01121 66th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed multiqueue2 (crates.io): 0.1.7

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
—multiqueue2 (crates.io)before 0.1.70.1.7Patch availableGHSA-jphw-p3m6-pj3c
  • — Vendor— Affected all versions Fixed in — No fix listed CNA
  • multiqueue2 (crates.io) Vendor— Affected before 0.1.7 Fixed in 0.1.7 Patch available GHSA-jphw-p3m6-pj3c

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:multiqueue2_project:multiqueue2:*:*:*:*:*:rust:*:*before 0.1.7VulnerableMultiqueue2 Project
  • cpe:2.3:a:multiqueue2_project:multiqueue2:*:*:*:*:*:rust:*:* Versions before 0.1.7 Vulnerable ·Multiqueue2 Project

Remediation

  • Fix · GHSA-jphw-p3m6-pj3c multiqueue2 (crates.io) Fixed in 0.1.7 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2020-36214
  2. 2026-10-03 Alias added: GHSA-jphw-p3m6-pj3c

References

Sources