Skip to content
Fencer Intel
medium —

GHSA-5qv7-j6w5-fr4m json

imageproc has fragile bounds check when sampling from image

published 6mo ago modified 6mo ago also RUSTSEC-2026-0115

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

A read of pixels was coded as modifying coordinates to lie within the image bounds. It would calculate a coordinate by adding a constant to an input and taking the minimum of the resulting coordinate and 'dimension - 1'. This would not protect against malicious inputs that could overflow the addition. Following the tricked bounds check, the image could then be sampled at multiple differently calculated coordinates that exceeded the bounds.

Patch / fix

  • crates.io imageproc 0.24.1, 0.25.1, 0.26.2

Is GHSA-5qv7-j6w5-fr4m 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 imageproc
>=0.24.0, <0.24.1
>=0.25.0, <0.25.1
>=0.26.0, <0.26.2
0.24.1
0.25.1
0.26.2

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

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.