Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
HIGH severity

Slock<T> allows sending non-Send types across thread boundariesGHSA-83r8-p8v6-6gfm

HIGH

GHSA-83r8-p8v6-6gfm is a high-severity (CVSS 8.1) CWE-77 vulnerability in slock. 1 public exploit reference exists, so weaponization risk is real. A fix is available for slock — see the affected versions and patch details below.

Also known asCVE-2020-36455GHSA-mc36-5m36-hjh5RUSTSEC-2020-0135
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk
0.01%0.61%1.21%1.81%0.5%1.3%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-83r8-p8v6-6gfm by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🦀slock

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Slock<T> unconditionally implements Send/Sync.

Affected versions of this crate allows sending non-Send types to other threads, which can lead to data races and memory corruption due to the data race.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioslockall versions0.2.0cargo update -p slock --precise 0.2.0

Affected Products

1 product · 1 configurations
Application
slockbrokenlamp
≤ 2020-11-17
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue was discovered in the slock crate through 2020-11-17 for Rust. …

rustsec.orgNVDAug 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for slock, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update slock to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-83r8-p8v6-6gfm is resolved across your whole dependency graph.

  3. Workarounds

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

`Slock<T>` unconditionally implements `Send`/`Sync`. Affected versions of this crate allows sending non-Send types to other threads, which can lead to data races and memory corruption due to the data race.
O3 Security · Impact-Aware SCA

Is GHSA-83r8-p8v6-6gfm in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
Slock<T> allows sending non-Send types across thread…