raster - Integer Underflow in crop() Offset Handling Causes Capacity-Overflow Panic

published 2026-08-05 3 mo ago modified 2026-10-24 15 d ago also EUVD-2026-53199

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits: 0; none known

The raster Rust crate's crop function (src/editor.rs) clamps the crop width/height against source dimensions but only clamps the offset_x/offset_y parameters against 0, never against the source width/height.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-71202 updated 2026-10-30 cvss 7.5

raster: Raster: Denial of Service via integer underflow in image cropping function

Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/cluster-logging-rhel9-operator
not affected: vulnerable code not present
Red Hat OpenShift Container Platform 4 openshift4/ose-tests-rhel9 Red Hat OpenShift Container Platform 5 openshift5/ose-tests-rhel9
not affected: vulnerable code not in execute path

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 3 mo ago (2026-08-05)

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/kosinix/raster/issues/30 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

kosinix raster

Classification

Weakness

CWE-191 Integer Underflow (Wrap or Wraparound)

References

github.com /kosinix/raster/issues/30
third-party-advisory, exploit

Sources

CVE List CVE-2026-71202
NVD CVE-2026-71202

Fencer Vulns 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.

Summary