{"id":"CVE-2020-36436","aliases":["EUVD-2021-1592","GHSA-686f-ch3r-xwmh","RUSTSEC-2020-0116"],"status":"published","title":"Data races in unicycle","description":"An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab\u003cT\u003e and Unordered\u003cT, S\u003e do not have bounds on their Send and Sync traits.","severity":{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-10","score":0.00766,"percentile":0.55782,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-119","CWE-362"],"published":"2020-11-15T12:00:00Z","modified":"2026-06-17T03:15:29Z","fixes":[{"ecosystem":"crates.io","package":"unicycle","fixed_in":["0.7.1"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"unicycle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.7.1"}]}]},{"source":"osv","ecosystem":"crates.io","package":"unicycle","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.7.1"}]}]},{"source":"osv","ecosystem":"crates.io","package":"unicycle","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.7.1"}]}]}],"products":[{"vendor":"unicycle_project","product":"unicycle"}],"references":[{"url":"https://rustsec.org/advisories/RUSTSEC-2020-0116.html","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","web","advisory"]},{"url":"https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/unicycle/RUSTSEC-2020-0116.md","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-36436","tags":["advisory"]},{"url":"https://github.com/udoprog/unicycle/issues/8","tags":["web","report"]},{"url":"https://github.com/udoprog/unicycle/commit/6a6c367a0c25f86f998fa315ea90c328f685b194","tags":["web"]},{"url":"https://github.com/udoprog/unicycle/commit/92f40b4a2c671553dfa96feacff0265206c44ce5","tags":["web"]},{"url":"https://github.com/advisories/GHSA-686f-ch3r-xwmh"},{"url":"https://github.com/udoprog/unicycle","tags":["package"]},{"url":"https://crates.io/crates/unicycle","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2020-36436","description":"An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab\u003cT\u003e and Unordered\u003cT, S\u003e do not have bounds on their Send and Sync traits.","status":"published","published":"2021-08-08T05:18:56Z","modified":"2024-08-04T17:30:08.159Z","updated_at":"2026-11-02T14:35:54.80237Z"}],"euvd":[{"id":"EUVD-2021-1592","description":"An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab\u003cT\u003e and Unordered\u003cT, S\u003e do not have bounds on their Send and Sync traits.","status":"published","published":"2021-08-08T05:18:56Z","modified":"2024-08-04T17:30:08Z","updated_at":"2026-11-03T03:07:03.010139Z"}],"ghsa":[{"id":"GHSA-686f-ch3r-xwmh","title":"Data races in unicycle","description":"Affected versions of this crate unconditionally implemented `Send` \u0026 `Sync` for types `PinSlab\u003cT\u003e` \u0026 `Unordered\u003cT, S\u003e`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.\n\nThis can result in a data race \u0026 memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab\u003cT\u003e` or `Unordered\u003cT, S\u003e` and accessed concurrently from multiple threads.\n\nThe flaw was corrected in commits 92f40b4 \u0026 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab\u003cT\u003e` \u0026 `Unordered\u003cT, S\u003e` and adding `T: Sync` to `Sync` impls for `PinSlab\u003cT\u003e` \u0026 `Unordered\u003cT, S\u003e`.","status":"published","published":"2021-08-25T20:58:17Z","modified":"2023-01-27T05:00:53Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-119","CWE-362"],"updated_at":"2026-11-02T14:36:15.574072Z"}],"nvd":[{"id":"CVE-2020-36436","description":"An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab\u003cT\u003e and Unordered\u003cT, S\u003e do not have bounds on their Send and Sync traits.","status":"published","published":"2021-08-08T06:15:06.967Z","modified":"2026-06-17T03:15:29.3Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":6.8,"vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-362"],"updated_at":"2026-11-02T14:06:44.292752Z"}],"osv":[{"id":"GHSA-686f-ch3r-xwmh","title":"Data races in unicycle","description":"Affected versions of this crate unconditionally implemented `Send` \u0026 `Sync` for types `PinSlab\u003cT\u003e` \u0026 `Unordered\u003cT, S\u003e`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.\n\nThis can result in a data race \u0026 memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab\u003cT\u003e` or `Unordered\u003cT, S\u003e` and accessed concurrently from multiple threads.\n\nThe flaw was corrected in commits 92f40b4 \u0026 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab\u003cT\u003e` \u0026 `Unordered\u003cT, S\u003e` and adding `T: Sync` to `Sync` impls for `PinSlab\u003cT\u003e` \u0026 `Unordered\u003cT, S\u003e`.","status":"published","published":"2021-08-25T20:58:17Z","modified":"2023-11-08T04:03:44.721625Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-119","CWE-362"],"updated_at":"2026-11-02T15:46:39.266402Z"},{"id":"RUSTSEC-2020-0116","title":"PinSlab\u003cT\u003e and Unordered\u003cT, S\u003e need bounds on their Send/Sync traits","description":"Affected versions of this crate unconditionally implemented `Send` \u0026 `Sync` for types `PinSlab\u003cT\u003e` \u0026 `Unordered\u003cT, S\u003e`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.\n\nThis can result in a data race \u0026 memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab\u003cT\u003e` or `Unordered\u003cT, S\u003e` and accessed concurrently from multiple threads.\n\nThe flaw was corrected in commits 92f40b4 \u0026 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab\u003cT\u003e` \u0026 `Unordered\u003cT, S\u003e` and adding `T: Sync` to `Sync` impls for `PinSlab\u003cT\u003e` \u0026 `Unordered\u003cT, S\u003e`.","status":"published","published":"2020-11-15T12:00:00Z","modified":"2023-11-08T04:03:44.721625Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:39.492624Z"}]}}