Rust advisories / fuser
Unsound HighRUSTSEC-2021-0154 · fuser
RUSTSEC-2021-0154: Uninitalized memory read & leak caused by fuser crate
Short answerfuser has an API that can cause undefined behaviour from safe code: Uninitalized memory read & leak caused by fuser crate. Fixed in 0.16.0.
| Crate | fuser |
|---|---|
| Type | Unsound (code-execution) |
| Affected versions | Before 0.16.0. |
| Fixed in | 0.16.0 |
| Severity | High (GitHub rating) |
| Published | 2021-09-10 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-cvmj-47v9-35m9 |
| Affected functions | fuser::Session::new |
What to do
- See which version you have:
cargo tree -i fuser(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p fuser. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplefuser = "0.16.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
During creation of new libfuse session with fuse_session_new operation list was passed as NULL incorrectly. libfuse expects this argument to always point to list of operations. This caused uninitialized memory read and leaks in libfuse.so
References
- Package: crates.io/crates/fuser
- Advisory: rustsec.org/advisories/RUSTSEC-2021-0154.html
- Web: github.com/cberner/fuser/pull/390
- Web: github.com/libfuse/libfuse/pull/1330
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
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?