Most recent entries from all

cnvd-2021-85300

2026-10-19T17:09:57.194777+00:00

cnvd-2021-85300

EUVD-2026-48192

2026-10-19T17:09:57.194822+00:00

EUVD-2026-48192

fkie_cve-2020-36435

2026-10-19T17:09:57.194838+00:00

An issue was discovered in the ruspiro-singleton crate before 0.4.1 for Rust. In Singleton, Send and Sync do not have bounds checks.

GHSA-fqq2-xp7m-xvm8 — Data race in ruspiro-singleton

2026-10-19T17:09:57.194868+00:00

Affected: crates.io: ruspiro-singleton

`Singleton` is meant to be a static object that can be initialized lazily. In order to satisfy the requirement that `static` items must implement `Sync`, `Singleton` implemented both `Sync` and `Send` unconditionally.

This allows for a bug where non-`Sync` types such as `Cell` can be used in singletons and cause data races in concurrent programs.

The flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring the contaiend type to implement `Sync`.

gsd-2020-36435

2026-10-19T17:09:57.194896+00:00

gsd-2020-36435

RUSTSEC-2020-0115 — Singleton lacks bounds on Send and Sync.

2026-10-19T17:09:57.194908+00:00

Affected: crates.io: ruspiro-singleton

This allows for a bug where non-`Sync` types such as `Cell` can be used in singletons and cause data races in concurrent programs.

The flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring the contaiend type to implement `Sync`.