# CVE-2026-22879: Memory corruption in vtk

> A heap-based buffer overflow in vtk-dicom allows attackers to execute arbitrary code or cause denial of service via a malicious DICOM file.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 23 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-22879, GHSA-prp5-qv62-frpc, JLSEC-2026-633, UBUNTU-CVE-2026-22879

## What is CVE-2026-22879?

CVE-2026-22879 is a high-severity memory corruption vulnerability in vtk, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap-based buffer overflow vulnerability exists in the vtkDICOMItem::FindDataElementOrInsert functionality of vtk-dicom (version(s): 9.5.2). A specially crafted DICOM file can lead to heap-based memory corruption. An attacker can provide a malicious file to trigger this vulnerability.

Weakness: CWE-129 (Improper Validation of Array Index)

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


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

Upgrade to a fixed version.

## Is CVE-2026-22879 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22879 is a high-severity memory corruption vulnerability in vtk, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22879 in the wild and no public exploit code.

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

## Sources

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

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