RUSTSEC-2026-0130: Out-of-bounds read/write in `Index` and `IndexMut` implementations

What to do

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

The Index and IndexMut implementations for Caja use unchecked pointer arithmetic without bounds validation. Creating a Caja with a small key and then accessing an out-of-range index causes out-of-bounds reads or writes beyond the allocated memory.

This can be triggered through safe public APIs , the [] indexing operator on a Caja with an out-of-range index , with no unsafe required from the caller.

References

• Package: crates.io/crates/caja
• Advisory: rustsec.org/advisories/RUSTSEC-2026-0130.html
• Report: github.com/EmanuelGCC/Caja/issues/1

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