# CVE-2026-3282: libvips unpremultiply.c vips_unpremultiply_build out-of-bounds

> A local attacker can trigger an out-of-bounds read in libvips via the alpha_band argument, potentially causing information disclosure or crashes.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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:** 27 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** DEBIAN-CVE-2026-3282, GHSA-pg5c-mhhq-cqhh, UBUNTU-CVE-2026-3282

## What is CVE-2026-3282?

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

### Official description

A flaw has been found in libvips 8.19.0. This vulnerability affects the function vips_unpremultiply_build of the file libvips/conversion/unpremultiply.c. Executing a manipulation of the argument alpha_band can lead to out-of-bounds read. The attack needs to be launched locally. The exploit has been published and may be used. This patch is called 7215ead1e0cd7d3703cc4f5fca06d7d0f4c22b91. A patch should be applied to remediate this issue.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Libvips Libvips.

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

Apply the vendor's patch.

## Is CVE-2026-3282 being exploited?

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

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

## Sources

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

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