futures-task
Zero-cost asynchronous programming in Rust
View on Github
Activity
- Latest release
- 1mo ago
- Total releases
- 36
- Cadence
- ~39 days
- Last 12 months
- 3
Reach
- Stars
- 5.9k
Details
- License
- MIT OR Apache-2.0
- First release
- Jul 29, 2019
| Version | Released | |
|---|---|---|
0.3.34
patch
| ||
0.3.33
unknown
| ||
0.3.32
unknown
| ||
0.3.31
unknown
| ||
0.3.30
unknown
| ||
0.3.29
unknown
| ||
0.3.28
unknown
| ||
0.3.27
unknown
| ||
0.3.26
unknown
| ||
0.3.25
unknown
| ||
0.3.24
unknown
| ||
0.3.23
unknown
| ||
0.3.22
unknown
| ||
0.3.21
unknown
| ||
0.3.20
unknown
yanked
| ||
0.3.19
unknown
| ||
0.3.18
unknown
yanked
| ||
0.3.17
unknown
| ||
0.3.16
unknown
| ||
0.3.15
unknown
| ||
0.3.14
unknown
| ||
0.3.13
unknown
| ||
0.3.12
unknown
| ||
0.3.11
unknown
| ||
0.3.10
unknown
| ||
0.3.9
unknown
| ||
0.3.8
unknown
| ||
0.3.7
unknown
| ||
0.3.6
unknown
| ||
0.3.5
unknown
1 CVE
CVE-2020-35906
GHSA-r93v-9p5q-vhpf
RUSTSEC-2020-0060
May 24, 2022
futures_task::waker may cause a use-after-free if used on a type that isn't 'static
7.8
/ 10
High
Local
Low
Low
None
Unchanged
High
High
High
Affected versions of the crate did not properly implement a 'static lifetime bound on the waker function. This resulted in a use-after-free if Waker::wake() is called after original data had been dropped. The flaw was corrected by adding 'static lifetime bound to the data waker takes. Fixed in
0.3.6
References Updated Oct 30, 2025 · Source: OSV.dev | ||
0.3.4
unknown
2 CVEs
CVE-2020-35907
GHSA-p9m5-3hj7-cp5r
RUSTSEC-2020-0061
May 24, 2022
futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
Affected versions of the crate used a UnsafeCell in thread-local storage to return a noop waker reference, assuming that the reference would never be returned from another thread. This resulted in a segmentation fault crash if Waker::wake_by_ref() was called on a waker returned from another thread due to it attempting to dereference a pointer that wasn't accessible from the main thread. Fixed in
0.3.5
References Updated Nov 08, 2023 · Source: OSV.dev
CVE-2020-35906
GHSA-r93v-9p5q-vhpf
RUSTSEC-2020-0060
May 24, 2022
futures_task::waker may cause a use-after-free if used on a type that isn't 'static
7.8
/ 10
High
Local
Low
Low
None
Unchanged
High
High
High
Affected versions of the crate did not properly implement a 'static lifetime bound on the waker function. This resulted in a use-after-free if Waker::wake() is called after original data had been dropped. The flaw was corrected by adding 'static lifetime bound to the data waker takes. Fixed in
0.3.6
References Updated Oct 30, 2025 · Source: OSV.dev | ||
0.3.3
unknown
2 CVEs
CVE-2020-35907
GHSA-p9m5-3hj7-cp5r
RUSTSEC-2020-0061
May 24, 2022
futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
Affected versions of the crate used a UnsafeCell in thread-local storage to return a noop waker reference, assuming that the reference would never be returned from another thread. This resulted in a segmentation fault crash if Waker::wake_by_ref() was called on a waker returned from another thread due to it attempting to dereference a pointer that wasn't accessible from the main thread. Fixed in
0.3.5
References Updated Nov 08, 2023 · Source: OSV.dev
CVE-2020-35906
GHSA-r93v-9p5q-vhpf
RUSTSEC-2020-0060
May 24, 2022
futures_task::waker may cause a use-after-free if used on a type that isn't 'static
7.8
/ 10
High
Local
Low
Low
None
Unchanged
High
High
High
Affected versions of the crate did not properly implement a 'static lifetime bound on the waker function. This resulted in a use-after-free if Waker::wake() is called after original data had been dropped. The flaw was corrected by adding 'static lifetime bound to the data waker takes. Fixed in
0.3.6
References Updated Oct 30, 2025 · Source: OSV.dev | ||
0.3.2
unknown
2 CVEs
CVE-2020-35907
GHSA-p9m5-3hj7-cp5r
RUSTSEC-2020-0061
May 24, 2022
futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
Affected versions of the crate used a UnsafeCell in thread-local storage to return a noop waker reference, assuming that the reference would never be returned from another thread. This resulted in a segmentation fault crash if Waker::wake_by_ref() was called on a waker returned from another thread due to it attempting to dereference a pointer that wasn't accessible from the main thread. Fixed in
0.3.5
References Updated Nov 08, 2023 · Source: OSV.dev
CVE-2020-35906
GHSA-r93v-9p5q-vhpf
RUSTSEC-2020-0060
May 24, 2022
futures_task::waker may cause a use-after-free if used on a type that isn't 'static
7.8
/ 10
High
Local
Low
Low
None
Unchanged
High
High
High
Affected versions of the crate did not properly implement a 'static lifetime bound on the waker function. This resulted in a use-after-free if Waker::wake() is called after original data had been dropped. The flaw was corrected by adding 'static lifetime bound to the data waker takes. Fixed in
0.3.6
References Updated Oct 30, 2025 · Source: OSV.dev | ||
0.3.1
unknown
2 CVEs
CVE-2020-35907
GHSA-p9m5-3hj7-cp5r
RUSTSEC-2020-0061
May 24, 2022
futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
Affected versions of the crate used a UnsafeCell in thread-local storage to return a noop waker reference, assuming that the reference would never be returned from another thread. This resulted in a segmentation fault crash if Waker::wake_by_ref() was called on a waker returned from another thread due to it attempting to dereference a pointer that wasn't accessible from the main thread. Fixed in
0.3.5
References Updated Nov 08, 2023 · Source: OSV.dev
CVE-2020-35906
GHSA-r93v-9p5q-vhpf
RUSTSEC-2020-0060
May 24, 2022
futures_task::waker may cause a use-after-free if used on a type that isn't 'static
7.8
/ 10
High
Local
Low
Low
None
Unchanged
High
High
High
Affected versions of the crate did not properly implement a 'static lifetime bound on the waker function. This resulted in a use-after-free if Waker::wake() is called after original data had been dropped. The flaw was corrected by adding 'static lifetime bound to the data waker takes. Fixed in
0.3.6
References Updated Oct 30, 2025 · Source: OSV.dev | ||
0.3.0
unknown
2 CVEs
CVE-2020-35907
GHSA-p9m5-3hj7-cp5r
RUSTSEC-2020-0061
May 24, 2022
futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
Affected versions of the crate used a UnsafeCell in thread-local storage to return a noop waker reference, assuming that the reference would never be returned from another thread. This resulted in a segmentation fault crash if Waker::wake_by_ref() was called on a waker returned from another thread due to it attempting to dereference a pointer that wasn't accessible from the main thread. Fixed in
0.3.5
References Updated Nov 08, 2023 · Source: OSV.dev
CVE-2020-35906
GHSA-r93v-9p5q-vhpf
RUSTSEC-2020-0060
May 24, 2022
futures_task::waker may cause a use-after-free if used on a type that isn't 'static
7.8
/ 10
High
Local
Low
Low
None
Unchanged
High
High
High
Affected versions of the crate did not properly implement a 'static lifetime bound on the waker function. This resulted in a use-after-free if Waker::wake() is called after original data had been dropped. The flaw was corrected by adding 'static lifetime bound to the data waker takes. Fixed in
0.3.6
References Updated Oct 30, 2025 · Source: OSV.dev | ||
0.0.0
unknown
1 CVE
CVE-2020-35907
GHSA-p9m5-3hj7-cp5r
RUSTSEC-2020-0061
May 24, 2022
futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer
5.5
/ 10
Medium
Local
Low
Low
None
Unchanged
None
None
High
Affected versions of the crate used a UnsafeCell in thread-local storage to return a noop waker reference, assuming that the reference would never be returned from another thread. This resulted in a segmentation fault crash if Waker::wake_by_ref() was called on a waker returned from another thread due to it attempting to dereference a pointer that wasn't accessible from the main thread. Fixed in
0.3.5
References Updated Nov 08, 2023 · Source: OSV.dev |