# CVE-2026-2913: libvips source.c vips_source_read_to_memory heap-based overflow

> A heap-based buffer overflow in libvips allows local attackers to cause a denial of service via custom seekable sources larger than 4 GiB.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** DEBIAN-CVE-2026-2913, GHSA-qjwf-h778-47mm, UBUNTU-CVE-2026-2913

## What is CVE-2026-2913?

CVE-2026-2913 is a low-severity memory corruption vulnerability in libvips, published on 22 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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)."

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-2913?

It affects 1 product.


Products: Libvips Libvips.

## How do I fix CVE-2026-2913?

Apply the vendor's patch.

## Is CVE-2026-2913 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2913 exists.

## Other vulnerabilities in libvips

- [CVE-2019-17534](https://insights.sbomify.com/CVE-2019-17534/): Use after free in n/a (high 8.8)
- [CVE-2026-33327](https://insights.sbomify.com/CVE-2026-33327/): Possible integer overflow leading to potential heap-based buffer overflow (high 7.0)
- [CVE-2026-35591](https://insights.sbomify.com/CVE-2026-35591/): Possible heap-based buffer overflow when decoding TIFF image containing well-crafted tile (high 7.0)
- [CVE-2026-33328](https://insights.sbomify.com/CVE-2026-33328/): Possible integer overflow on 32-bit systems when reading GIF images (medium 6.8)
- [CVE-2026-35590](https://insights.sbomify.com/CVE-2026-35590/): Possible out-of-bounds read leading to crash when decoding well-crafted EXIF metadata (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2913 and fix it if it is affected.

What it is: CVE-2026-2913 is a low-severity memory corruption vulnerability in libvips, published on 22 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2913 exists.

Affected product: libvips. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2913/ (Markdown: https://insights.sbomify.com/CVE-2026-2913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2913
- OSV: https://osv.dev/vulnerability/CVE-2026-2913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2913/
Summaries are generated and may contain mistakes; the official description above is the record.