CVE-2026-70654

Process crash via max/min read-size confusion

Published Aug 20, 2026 · Updated Aug 20, 2026

Heap buffer overflow in libvips before 8.18.3 allows local users to crash a process via crafted uncompressed PPM input from a custom source. In vips_source_read_to_memory in libvips/iofuncs/source.c, the remaining byte count is chosen with VIPS_MAX instead of VIPS_MIN, so a read can write up to 4032 bytes past the allocated heap buffer. Reachability is limited to applications that implement unusual custom libvips sources and pass untrusted uncompressed PPM data through that path; the published impact is memory corruption or a process crash.

CVSS severity5.8
Medium
EPSS probability0.11%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Heap buffer overflow in libvips before 8.18.3 allows local users to crash a process via crafted uncompressed PPM input from a custom source. In vips_source_read_to_memory in libvips/iofuncs/source.c, the remaining byte count is chosen with VIPS_MAX instead of VIPS_MIN, so a read can write up to 4032 bytes past the allocated heap buffer. Reachability is limited to applications that implement unusual custom libvips sources and pass untrusted uncompressed PPM data through that path; the published impact is memory corruption or a process crash.

The record

CVE
CVE-2026-70654
Published
Aug 20, 2026
Updated
Aug 20, 2026
Vendor
libvips
Product
libvips
Classifications
CWE-122
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 8.18.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

libvips · libvipsversion=< 8.18.3

Published CVSS scores

5.8GitHub, Inc.CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-122Heap-based Buffer Overflow

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo