Skip to content

← Actionable
Medium, CVSS 6.9

imageproc: Out-of-bounds read via NaN coordinates in bilinear/bicubic sampling

GHSA-qg8r-f7x3-25f7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (imageproc 0.26.2, 0.25.1, 0.24.1, 0.23.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • crates.io imageproc

    Affected
    < 0.23.1>= 0.24.0, <= 0.24.0>= 0.25.0, <= 0.25.0>= 0.26.0, < 0.26.2
    Fixed in
    0.25.1, 0.24.1, 0.23.1, 0.26.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-qg8r-f7x3-25f7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-qg8r-f7x3-25f7

Advisory: imageproc: Out-of-bounds read via NaN coordinates in bilinear/bicubic sampling
IDs: GHSA-qg8r-f7x3-25f7
Record: https://patchnext.com/advisories/ghsa-qg8r-f7x3-25f7 (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: imageproc 0.26.2, 0.25.1, 0.24.1, 0.23.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io imageproc: affected < 0.23.1; >= 0.24.0, <= 0.24.0; >= 0.25.0, <= 0.25.0; >= 0.26.0, < 0.26.2; fixed in 0.25.1, 0.24.1, 0.23.1, 0.26.2

## Suggested inspection (read-only)
- crates.io imageproc: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on imageproc.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qg8r-f7x3-25f7 (GitHub-reviewed advisory GHSA-qg8r-f7x3-25f7 lists affected ranges: crates.io imageproc >=0 =0.24.0 =0.25.0 =0.26.0 <0.26.2)

Commands are suggestions: review each one before running it.

Loading voting…