Back to CVE records
High 7.0Published Feb 22, 2026

CVE-2026-2913A vulnerability was determined in libvips up to 8.19.0.

Updated under an hour ago ()

Does this affect you?

It affects libvips. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

A vulnerability was determined in libvips up to 8.19.0. The affected element is the function vips_source_read_to_memory of the file libvips/iofuncs/source.c. This manipulation causes heap-based buffer overflow. It is possible to launch the attack on the local host. The attack's complexity is rated as high. The exploitability is described as difficult. The exploit has been publicly disclosed and may be utilized. Patch name: a56feecbe9ed66521d9647ec9fbcd2546eccd7ee. Applying a patch is the recommended action to fix this issue. The confirmation of the bugfix mentions: "[T]he impact of this is negligible, since this only affects custom seekable sources larger than 4 GiB (and the crash occurs in user code rather than libvips itself)."

CVSS
7.0 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-119, CWE-122
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Not given
NVD analysis
Analyzed
Record last updated
Jun 17, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
libvips libvips
libvips:libvips
through 8.19.0
NVD

References

  • product
  • patch
  • issue-tracking
  • exploit, issue-tracking
  • exploit, issue-tracking
  • permissions-required, vdb-entry
  • third-party-advisory, vdb-entry
  • third-party-advisory, vdb-entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.