RUSTSEC-2023-0039: Out-of-bounds array access leads to panic

What to do

1. See which version you have: cargo tree -i buffered-reader (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p buffered-reader. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example buffered-reader = "1.2.0") 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

Affected versions of the crate have a bug where attacker-controlled input can result in the use of an out-of-bound array index. Rust detects the use of the out-of-bound index and causes the application to panic. An attacker may be able to use this to cause a denial-of-service. However, it is not possible for an attacker to read from or write to the application's address space.

References

• Package: crates.io/crates/buffered-reader
• Advisory: rustsec.org/advisories/RUSTSEC-2023-0039.html
• Web: lists.sequoia-pgp.org/hyperkitty/list/announce@lists.sequoia-pgp.org/thread/SN2E3QRT4DMQ5JNEK6VIN6DJ5SH766DI/
• Web: gitlab.com/sequoia-pgp/sequoia/-/tags/buffered-reader%2Fv1.2.0

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