Skip to content
Fencer Vulns
medium 4.7

CVE-2020-35913 json

An issue was discovered in the lock_api crate before 0.4.2 for Rust.

published 2020-12-31 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-1749

cvss
4.7
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits
0
none known

Summary

An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.

Patch / fix

  • lock_api_project lock_api 0.4.2
  • rust-lock-api Debian 14, Debian 13, Debian 12 0.4.5-1

debian advisories DEBIAN-CVE-2020-35913

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.