CVE-2026-22879 json
vtk vtk-dicom vtkDICOMItem::NewDataElement heap-based buffer overflow vulnerability
published 2026-06-25 4 mo ago modified 2026-09-23 47 d ago also EUVD-2026-39582 , GHSA-prp5-qv62-frpc , JLSEC-2026-633
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- julia VTK_jll 9.6.1+0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-22879 updated cvss 8.1
vtk: vtk-dicom: vtk-dicom: Arbitrary code execution via heap-based buffer overflow in vtkDICOMItem::NewDataElement
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 4 mo ago
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| julia | VTK_jll | >=9.5.2+0, <9.6.1+0 |
9.6.1+0 |
Affected products
- vtk vtk
Classification
- Weakness
-
- CWE-129 Improper Validation of Array Index
References
Sources
- CVE List CVE-2026-22879
- NVD CVE-2026-22879
- OSV JLSEC-2026-633
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.