# CVE-2026-3147: libvips csvload.c vips_foreign_load_csv_build heap-based overflow

> A heap-based buffer overflow in libvips allows local attackers to execute arbitrary code or cause denial of service via crafted CSV files.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/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:** 25 Feb 2026
- **Updated:** 25 Feb 2026
- **Also known as:** DEBIAN-CVE-2026-3147, GHSA-55xf-4pmg-v3xm, UBUNTU-CVE-2026-3147

## What is CVE-2026-3147?

CVE-2026-3147 is a medium-severity memory corruption vulnerability in libvips, published on 25 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 found in libvips up to 8.18.0. This affects the function vips_foreign_load_csv_build of the file libvips/foreign/csvload.c. The manipulation results in heap-based buffer overflow. The attack requires a local approach. The exploit has been made public and could be used. The patch is identified as b3ab458a25e0e261cbd1788474bbc763f7435780. It is advisable to implement a patch to correct this issue.

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-3147?

It affects 1 product.


Products: Libvips Libvips.

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

Apply the vendor's patch.

## Is CVE-2026-3147 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3147 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-3147 and fix it if it is affected.

What it is: CVE-2026-3147 is a medium-severity memory corruption vulnerability in libvips, published on 25 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-3147 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-3147/ (Markdown: https://insights.sbomify.com/CVE-2026-3147/index.md)
```

## Sources

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

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