dbcve.org
LibvipsApplication

CVE-2026-2913

HIGH · 7.0 CVSS v3.1 Published 2026-02-22
Fix available
A fix is available. Upgrade to after 8.19.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Public exploit Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-119

The program reads or writes outside the bounds of an allocated buffer, corrupting adjacent memory. With crafted input an attacker can overwrite control data and, with effort, redirect execution to their own code. Remediation ranges from bounds checking and safe library functions to compiler mitigations, usually alongside a careful audit of the surrounding code.

General guidance for the memory buffer bounds error class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibvipsApplication
Affected:<= 8.19.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 8.19.0
Vendor patch github.com →
Recommended fix Moderate confidence

libvips 8.19.1 or later (preferably latest stable release)

  1. 1. Identify the current libvips version installed: `pkg-config --modversion vips` or check your package manager
  2. 2. Upgrade to a version higher than 8.19.0 that includes the fix (commit a56feecbe9ed66521d9647ec9fbcd2546eccd7ee)
  3. 3. If using a package manager, run: `apt-get update && apt-get install libvips` (Debian/Ubuntu) or `yum update libvips` (RHEL/CentOS)
  4. 4. If building from source, download the source for version 8.19.1 or later from https://github.com/libvips/libvips/releases
  5. 5. Rebuild and reinstall the library, then rebuild any applications that link against libvips
  6. 6. Verify the new version is installed: `vips --version`
Caveat Applications dynamically linked to libvips will automatically use the new version; verify compatibility with any custom source handlers using vips_source_read_to_memory

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2913 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data