Unsound CriticalRUSTSEC-2022-0008 · windows
RUSTSEC-2022-0008: Delegate functions are missing `Send` bound
Short answerwindows has an API that can cause undefined behaviour from safe code: Delegate functions are missing `Send` bound. Fixed in 0.32.0.
| Crate | windows |
|---|---|
| Type | Unsound (memory-corruption, thread-safety) |
| Affected versions | From 0.1.2 before 0.32.0. |
| Fixed in | 0.32.0 |
| Severity | Critical (GitHub rating) |
| Published | 2022-01-02 |
| Last changed | 2023-11-08 |
| Also known as | GHSA-x4mq-m75f-mx8m |
What to do
- See which version you have:
cargo tree -i windows(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p windows. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplewindows = "0.32.0") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Affected versions of this crate did not require event handlers to have Send bound despite there being no guarantee of them being called on any particular thread, which can potentially lead to data races and undefined behavior.
The flaw was corrected in commit afe3252 by adding Send bounds.
References
- Package: crates.io/crates/windows
- Advisory: rustsec.org/advisories/RUSTSEC-2022-0008.html
- Report: github.com/microsoft/windows-rs/issues/1409
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Same cratewindows: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?