# CVE-2026-130888: nbdkit: qcow2dec ZSTD heap over-read via incorrect input buffer size

> A crafted QCOW2 image with ZSTD clusters causes a heap over-read in nbdkit, crashing applications or leaking heap memory.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-130888, DHI-gwpp-tdwn-uuef-3by7, GHSA-gr82-2frv-56jg, UBUNTU-CVE-2026-130888

## What is CVE-2026-130888?

CVE-2026-130888 is a medium-severity memory corruption vulnerability in nbdkit, published on 19 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A flaw was found in nbdkit. The qcow2dec filter's zstd_compressed_cluster() function incorrectly sets the ZSTD input buffer size to the uncompressed cluster size instead of the compressed buffer size. A crafted QCOW2 image with ZSTD-compressed clusters can trigger a heap over-read, leading to a denial of service and potentially exposing heap memory.

Weakness: CWE-125 (Out-of-bounds Read)

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2026-130888 being exploited?

There is no known exploitation of CVE-2026-130888 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130888 is a medium-severity memory corruption vulnerability in nbdkit, published on 19 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-130888 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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