{"id":"CVE-2020-36214","aliases":["EUVD-2021-1778","GHSA-jphw-p3m6-pj3c","RUSTSEC-2020-0106"],"status":"published","title":"Data races in multiqueue2","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.","severity":{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.01121,"percentile":0.66605,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-662"],"published":"2020-12-19T12:00:00Z","modified":"2026-06-17T03:15:01Z","fixes":[{"ecosystem":"crates.io","package":"multiqueue2","fixed_in":["0.1.7"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"multiqueue2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.1.7"}]}]},{"source":"osv","ecosystem":"crates.io","package":"multiqueue2","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.1.7"}]}]},{"source":"osv","ecosystem":"crates.io","package":"multiqueue2","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.1.7"}]}]}],"products":[{"vendor":"multiqueue2_project","product":"multiqueue2"}],"references":[{"url":"https://rustsec.org/advisories/RUSTSEC-2020-0106.html","tags":["x_refsource_MISC","x_transferred","Exploit","Vendor Advisory","web","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-36214","tags":["advisory"]},{"url":"https://github.com/abbychau/multiqueue2/issues/10","tags":["web","report"]},{"url":"https://github.com/advisories/GHSA-jphw-p3m6-pj3c"},{"url":"https://github.com/abbychau/multiqueue2","tags":["package"]},{"url":"https://crates.io/crates/multiqueue2","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2020-36214","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.","status":"published","published":"2021-01-22T09:05:01Z","modified":"2024-08-04T17:23:09.558Z","updated_at":"2026-11-02T14:35:55.128961Z"}],"euvd":[{"id":"EUVD-2021-1778","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.","status":"published","published":"2021-01-22T09:05:01Z","modified":"2024-08-04T17:23:09Z","updated_at":"2026-11-03T03:07:03.484914Z"}],"ghsa":[{"id":"GHSA-jphw-p3m6-pj3c","title":"Data races in multiqueue2","description":"Affected versions of this crate unconditionally implemented Send for types used in queue implementations (InnerSend\u003cRW, T\u003e, InnerRecv\u003cRW, T\u003e, FutInnerSend\u003cRW, T\u003e, FutInnerRecv\u003cRW, T\u003e).\n\nThis allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.\n\nThe flaw was corrected in v0.1.7 by adding T: Send bound to to the Send impl of four data types explained above.","status":"published","published":"2021-08-25T20:51:54Z","modified":"2023-06-13T20:04:08Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-662"],"updated_at":"2026-11-02T14:36:53.654352Z"}],"nvd":[{"id":"CVE-2020-36214","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.","status":"published","published":"2021-01-26T18:15:56.27Z","modified":"2026-06-17T03:15:01.563Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"},{"version":"2.0","score":4.3,"vector":"AV:N/AC:M/Au:N/C:N/I:N/A:P","level":"medium","assessor":"primary"}],"updated_at":"2026-11-02T14:06:30.596418Z"}],"osv":[{"id":"GHSA-jphw-p3m6-pj3c","title":"Data races in multiqueue2","description":"Affected versions of this crate unconditionally implemented Send for types used in queue implementations (InnerSend\u003cRW, T\u003e, InnerRecv\u003cRW, T\u003e, FutInnerSend\u003cRW, T\u003e, FutInnerRecv\u003cRW, T\u003e).\n\nThis allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.\n\nThe flaw was corrected in v0.1.7 by adding T: Send bound to to the Send impl of four data types explained above.","status":"published","published":"2021-08-25T20:51:54Z","modified":"2023-11-08T04:03:41.902458Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-662"],"updated_at":"2026-11-02T15:46:50.687609Z"},{"id":"RUSTSEC-2020-0106","title":"Queues allow non-Send types to be sent to other threads, allowing data races","description":"Affected versions of this crate unconditionally implemented `Send` for types used in queue implementations (`InnerSend\u003cRW, T\u003e`, `InnerRecv\u003cRW, T\u003e`, `FutInnerSend\u003cRW, T\u003e`, `FutInnerRecv\u003cRW, T\u003e`).\n\nThis allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.\n\nThe flaw was corrected in v0.1.7 by adding `T: Send` bound to to the `Send` impl of four data types explained above.","status":"published","published":"2020-12-19T12:00:00Z","modified":"2023-11-08T04:03:41.902458Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:53:39.492624Z"}]}}