CVE-2020-35906

Exp

An issue was discovered in the futures-task crate before 0.3.6 for Rust. futures_task::waker may cause a use-after-free in a non-static type situation.

Published: 2020-12-31 Last update: 2025-10-30 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-35906 is rated Exploit Available (56.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.13%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-35906

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-35906

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-03-30 0.29% 0.13% -0.16%
2 2025-03-29 0.14% 0.29% +0.16%
3 2025-03-17 — 0.14% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-35906

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.2 2.0 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 3.9 10.0 [email protected]

Weakness enumeration for CVE-2020-35906

GitHub Security Advisory for CVE-2020-35906

GHSA-r93v-9p5q-vhpf · Severity: high · Ecosystem: rust — futures_task::waker may cause a use-after-free if used on a type that isn't 'static

OS Trackers for CVE-2020-35906

vendor priority summary link
debian unimportant CVE-2020-35906 unimportant priority: Debian including 1 source packages (rust-futures-task), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-35906
ubuntu low CVE-2020-35906 low priority: Ubuntu including 1 source packages (rust-futures-task), 16 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 7, DNE 5, needs-triage 3, not-affected 1. https://ubuntu.com/security/CVE-2020-35906

Affected software / configurations for CVE-2020-35906

Vendor Product Version Raw CPE
rust-lang futures-task >= 0.2.1, < 0.3.6 cpe:2.3:a:rust-lang:futures-task:*:*:*:*:*:rust:*:*

References for CVE-2020-35906

URL Tags
https://rustsec.org/advisories/RUSTSEC-2020-0060.html Exploit Patch Third Party Advisory
cvelogic Threat Intelligence