Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0130 json

Out-of-bounds read/write in `Index` and `IndexMut` implementations

published 6mo ago modified 5mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

Patch / fix

  • crates.io caja 0.3.0

Is RUSTSEC-2026-0130 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io caja
>=0.0.0-0, <0.3.0
0.3.0

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.