Most recent entries from all

cnvd-2021-85298

2026-10-16T00:22:13.541810+00:00

cnvd-2021-85298

EUVD-2026-48189

2026-10-16T00:22:13.541853+00:00

EUVD-2026-48189

fkie_cve-2020-36437

2026-10-16T00:22:13.541876+00:00

An issue was discovered in the conqueue crate before 0.4.0 for Rust. There are unconditional implementations of Send and Sync for QueueSender.

GHSA-368f-29c3-4f2r — Data race in conqueue

2026-10-16T00:22:13.541925+00:00

Affected: crates.io: conqueue

Affected versions of this crate unconditionally implemented `Send`/`Sync` for `QueueSender`, allowing to send non-Send `T` to other threads by invoking `(&QueueSender).send()`.

This fails to prevent users from creating data races by sending types like `Rc` or `Arc>` to other threads, which can lead to memory corruption. The flaw was corrected in commit `1e462c3` by imposing `T: Send` to both `Send`/`Sync` impls for `QueueSender`/`QueueReceiver`.

gsd-2020-36437

2026-10-16T00:22:13.541972+00:00

gsd-2020-36437

RUSTSEC-2020-0117 — QueueSender/QueueReceiver: Send/Sync impls need `T: Send`

2026-10-16T00:22:13.541992+00:00

Affected: crates.io: conqueue

Affected versions of this crate unconditionally implemented `Send`/`Sync` for `QueueSender`, allowing to send non-Send `T` to other threads by invoking `(&QueueSender).send()`.

This fails to prevent users from creating data races by sending types like `Rc` or `Arc>` to other threads, which can lead to memory corruption.

The flaw was corrected in commit 1e462c3 by imposing `T: Send` to both `Send`/`Sync` impls for `QueueSender`/`QueueReceiver`.