# CVE-2026-88360: Denial of service in n/a

> An attacker can cause a denial of service in libvips by providing a malformed PFM image that triggers undefined behavior during processing.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 6 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-88360, GHSA-4f34-xv5x-8jfh, UBUNTU-CVE-2026-88360

## What is CVE-2026-88360?

CVE-2026-88360 is a high-severity denial of service vulnerability in n/a, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libvips 8.19.0 contains a memory access vulnerability when processing little-endian PFM images. If the PFM text header length is not a multiple of four bytes, the mmap-based loader can expose pixel data at an address that is not properly aligned for float access. vips_avg_scan() subsequently dereferences the buffer through a float pointer, resulting in undefined behavior and process termination on strict-alignment architectures or UBSan-instrumented builds, leading to denial of service.

Weakness: CWE-1339 (Insufficient Precision or Accuracy of a Real Number)

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


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

No fix has been published for CVE-2026-88360 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-88360 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88360 is a high-severity denial of service vulnerability in n/a, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88360 exists.

Affected product: n/a. 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-88360/ (Markdown: https://insights.sbomify.com/CVE-2026-88360/index.md)
```

## Sources

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

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