Rust advisories / fast-able
Vulnerability HighRUSTSEC-2025-0063 · fast-able
RUSTSEC-2025-0063: Possible unsound public API
Short answerA security vulnerability in the fast-able crate: Possible unsound public API. GitHub rates it High. Fixed in 1.13.7: update to a fixed version.
| Crate | fast-able |
|---|---|
| Type | Vulnerability (memory-corruption) |
| Affected versions | Before 1.13.7. |
| Fixed in | 1.13.7 |
| Severity | High (GitHub rating) |
| Published | 2025-04-25 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-95hm-pr6q-298w |
| Affected functions | fast_able::vec::SyncVec::get_unchecked |
What to do
- See which version you have:
cargo tree -i fast-able(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p fast-able. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplefast-able = "1.13.7") 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
The public accessible struct SyncVec has a public safe method get_unchecked. It accept a parameter index and used in the get_unchecked without sufficient checks as mentioned here.
References
- Package: crates.io/crates/fast-able
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0063.html
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?