RUSTSEC-2018-0001: An integer underflow could lead to panic

What to do

1. See which version you have: cargo tree -i untrusted (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p untrusted. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example untrusted = "0.6.2") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

A mistake in error handling in untrusted before 0.6.2 could lead to an integer underflow and panic if a user of the crate didn't properly check for errors returned by untrusted.

Combination of these two programming errors (one in untrusted and another by user of this crate) could lead to a panic and maybe a denial of service of affected software.

The error in untrusted is fixed in release 0.6.2 released 2018-06-21. It's also advisable that users of untrusted check for their sources for cases where errors returned by untrusted are not handled correctly.

References

• Package: crates.io/crates/untrusted
• Advisory: rustsec.org/advisories/RUSTSEC-2018-0001.html
• Web: github.com/briansmith/untrusted/pull/20

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.