https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-17T18:38:02.353994+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cnvd-2021-85299 cnvd-2021-85299 2026-10-17T18:38:02.452900+00:00 cnvd-2021-85299 https://cve.radiocsirt.org/vuln/euvd-2026-48221 EUVD-2026-48221 2026-10-17T18:38:02.452937+00:00 EUVD-2026-48221 https://cve.radiocsirt.org/vuln/fkie_cve-2020-36436 fkie_cve-2020-36436 2026-10-17T18:38:02.452962+00:00

An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab<T> and Unordered<T, S> do not have bounds on their Send and Sync traits.

 https://cve.radiocsirt.org/vuln/ghsa-686f-ch3r-xwmh GHSA-686f-ch3r-xwmh — Data races in unicycle 2026-10-17T18:38:02.452992+00:00

Affected: crates.io: unicycle

Affected versions of this crate unconditionally implemented `Send` & `Sync` for types `PinSlab<T>` & `Unordered<T, S>`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.

This can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab<T>` or `Unordered<T, S>` and accessed concurrently from multiple threads.

The flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab<T>` & `Unordered<T, S>` and adding `T: Sync` to `Sync` impls for `PinSlab<T>` & `Unordered<T, S>`.

 https://cve.radiocsirt.org/vuln/gsd-2020-36436 gsd-2020-36436 2026-10-17T18:38:02.453021+00:00 gsd-2020-36436 https://cve.radiocsirt.org/vuln/rustsec-2020-0116 RUSTSEC-2020-0116 — PinSlab<T> and Unordered<T, S> need bounds on their Send/Sync traits 2026-10-17T18:38:02.453033+00:00

Affected: crates.io: unicycle

Affected versions of this crate unconditionally implemented `Send` & `Sync` for types `PinSlab<T>` & `Unordered<T, S>`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.

This can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab<T>` or `Unordered<T, S>` and accessed concurrently from multiple threads.

The flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab<T>` & `Unordered<T, S>` and adding `T: Sync` to `Sync` impls for `PinSlab<T>` & `Unordered<T, S>`.