RUSTSEC-2026-0117: Fragile bounds check when sampling from image

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 check was performed in floating points before a cast to the index passed to an unchecked access function. This checked considered NaN cases improperly, causing them to succeed the check instead of failing it. The floating point coordinate is under caller control by passing a selected projection matrix.

Carefully controlling the coordinates of an image with no data and one non-zero dimension provides an arbitrary read primitive in the first 32-bits of address space with a Bilinear sampling method.

Using bicubic sampling can result in a read of a few bytes beyond an allocation.

Other out-of-bounds reads may be possible.

References

• Package: crates.io/crates/imageproc
• Advisory: rustsec.org/advisories/RUSTSEC-2026-0117.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-0116 · 2026-05-01Improper check of an invariant resulting in incorrect bounds checks

Full security history of imageproc