RUSTSEC-2026-0116: Improper check of an invariant resulting in incorrect bounds checks

What to do

1. See which version you have: cargo tree -i imageproc (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p imageproc. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example imageproc = "0.26.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 bounds verification of a slice storage of a 2-dimensional matrix's coefficients (a kernel) would compare the total size against the product of individual dimensions. This would erroneously cast *after* the multiplication and consequently fail to detect possible violations when overflow occurs.

Afterwards, the individual sizes were trusted to properly constrain coordinates within the matrix to indices valid for the underlying storage. With a crafted Kernel object, certain combinations of coordinates could then cause an out-of-bounds access in an unsafe function while fulfilling its documented preconditions. The kernel value could be passed to library functions that trusted the preconditions and then performed such reads.

References

• Package: crates.io/crates/imageproc
• Advisory: rustsec.org/advisories/RUSTSEC-2026-0116.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.

Other advisories for imageproc

• UnsoundRUSTSEC-2026-0115 · 2026-05-01Fragile bounds check when sampling from image
• UnsoundRUSTSEC-2026-0117 · 2026-05-01Fragile bounds check when sampling from image

Full security history of imageproc