GHSA-5qv7-j6w5-fr4m Fragile bounds check when sampling from image
Not scored
Published
Check this codebase for GHSA-5qv7-j6w5-fr4m and fix it if it is affected.
What it is: GHSA-5qv7-j6w5-fr4m is a vulnerability in imageproc, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-5qv7-j6w5-fr4m in the wild and no public exploit code.
Affected packages and fixed versions:
- imageproc (crates.io): affected from 0.24.0; fixed in 0.24.1, 0.25.1, 0.26.2
- imageproc (crates.io): affected from 0.24.0; fixed in 0.24.1
- imageproc (crates.io): affected from 0.24.0; fixed in 0.24.1
- imageproc (crates.io): affected from 0.25.0; fixed in 0.25.1
- imageproc (crates.io): affected from 0.25.0; fixed in 0.25.1
- imageproc (crates.io): affected from 0.26.0; fixed in 0.26.2
- imageproc (crates.io): affected from 0.26.0; fixed in 0.26.2
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/GHSA-5qv7-j6w5-fr4m/ (Markdown: https://insights.sbomify.com/GHSA-5qv7-j6w5-fr4m/index.md)
An integer overflow in bounds checking allows out-of-bounds memory reads when processing malicious images, potentially causing crashes or data leaks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-5qv7-j6w5-fr4m?
GHSA-5qv7-j6w5-fr4m is a vulnerability in imageproc, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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. .
Subsequently to the tricked bounds check the image could then be sampled at
multiple, differently calculated coordinates exceeding the bounds.
Which versions are affected by GHSA-5qv7-j6w5-fr4m?
7 open source packages ship an affected version, including imageproc.
| Package | Affected | Fixed in |
|---|---|---|
imageproc crates.io | From 0.24.0 | 0.24.1, 0.25.1, 0.26.2 |
imageproc crates.io | From 0.24.0 | 0.24.1 |
imageproc crates.io | From 0.24.0 | 0.24.1 |
imageproc crates.io | From 0.25.0 | 0.25.1 |
imageproc crates.io | From 0.25.0 | 0.25.1 |
imageproc crates.io | From 0.26.0 | 0.26.2 |
1 more packages
imageproc crates.io | From 0.26.0 | 0.26.2 |
How do I fix GHSA-5qv7-j6w5-fr4m?
Upgrade imageproc to a fixed version for your release line: 0.24.1, 0.25.1 or 0.26.2.
Is GHSA-5qv7-j6w5-fr4m being exploited?
There is no known exploitation of GHSA-5qv7-j6w5-fr4m in the wild and no public exploit code.
Sources
Also known as RUSTSEC-2026-0115.