https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 20:30:44 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-47884 EUVD-2026-47884 https://cve.radiocsirt.org/vuln/euvd-2026-47884 https://cve.radiocsirt.org/vuln/fkie_cve-2020-35908 <p>An issue was discovered in the futures-util crate before 0.3.2 for Rust. FuturesUnordered can lead to data corruption because Sync is mishandled.</p> <p>An issue was discovered in the futures-util crate before 0.3.2 for Rust. FuturesUnordered can lead to data corruption because Sync is mishandled.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2020-35908 https://cve.radiocsirt.org/vuln/ghsa-5r9g-j7jj-hw6c <p><strong>Affected:</strong> crates.io: futures-util</p> <p>An issue was discovered in the futures-util crate before 0.3.2 for Rust. FuturesUnordered can lead to data corruption because Sync is mishandled.</p> <p><strong>Affected:</strong> crates.io: futures-util</p> <p>An issue was discovered in the futures-util crate before 0.3.2 for Rust. FuturesUnordered can lead to data corruption because Sync is mishandled.</p> https://cve.radiocsirt.org/vuln/ghsa-5r9g-j7jj-hw6c https://cve.radiocsirt.org/vuln/gsd-2020-35908 gsd-2020-35908 https://cve.radiocsirt.org/vuln/gsd-2020-35908 https://cve.radiocsirt.org/vuln/rustsec-2020-0062 <p><strong>Affected:</strong> crates.io: futures-util</p> <p>Affected versions of the crate had an unsound `Sync` implementation on the `FuturesUnordered` structure, which used a `Cell` for interior mutability without any code to handle synchronized access to the underlying task list&#39;s length and head safely.</p> <p>This could of lead to data corruption since two threads modifying the list at once could see incorrect values due to the lack of access synchronization.</p> <p>The issue was fixed by adding access synchronization code around insertion of tasks into the list.</p> <p><strong>Affected:</strong> crates.io: futures-util</p> <p>Affected versions of the crate had an unsound `Sync` implementation on the `FuturesUnordered` structure, which used a `Cell` for interior mutability without any code to handle synchronized access to the underlying task list&#39;s length and head safely.</p> <p>This could of lead to data corruption since two threads modifying the list at once could see incorrect values due to the lack of access synchronization.</p> <p>The issue was fixed by adding access synchronization code around insertion of tasks into the list.</p> https://cve.radiocsirt.org/vuln/rustsec-2020-0062