NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

imageproc: Out-of-bounds read via NaN coordinates in bilinear/bicubic samplingGHSA-qg8r-f7x3-25f7

GHSA-qg8r-f7x3-25f7 is a security vulnerability in imageproc. A fix is available for imageproc — see the affected versions and patch details below.

Also known asRUSTSEC-2026-0117
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected
🦀imageproc🦀imageproc🦀imageproc🦀imageproc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioimageprocall versions0.23.1cargo update -p imageproc --precise 0.23.1
🦀crates.ioimageproc≥ 0.24.0&&< 0.24.10.24.1cargo update -p imageproc --precise 0.24.1
🦀crates.ioimageproc≥ 0.25.0&&< 0.25.10.25.1cargo update -p imageproc --precise 0.25.1
🦀crates.ioimageproc≥ 0.26.0&&< 0.26.20.26.2cargo update -p imageproc --precise 0.26.2

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for imageproc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update imageproc to 0.23.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qg8r-f7x3-25f7 is resolved across your whole dependency graph.

  3. Workarounds

    Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Frequently Asked Questions

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. Oth
O3 Security · Impact-Aware SCA

Is GHSA-qg8r-f7x3-25f7 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
imageproc: Out-of-bounds read via NaN coordinates in…