Loading vulnerability…
CVE-2026-22879 is a heap-based buffer overflow vulnerability in the vtk-dicom component of VTK, specifically in the vtkDICOMItem::NewDataElement function. The flaw is a memory corruption issue in which crafted DICOM data can trigger out-of-bounds writes on the heap during data element processing. The vulnerability is described as remotely exploitable and does not require privileges or user interaction, indicating that a vulnerable application can be compromised by processing attacker-controlled input delivered over a network or other untrusted source. The issue has been rated High severity with a CVSS v3.1 base score of 8.1.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A heap-based buffer overflow vulnerability in VTK-DICOM.
A heap-based buffer overflow vulnerability in VTK vtk-dicom, specifically in vtkDICOMItem::NewDataElement. It is significant because it is remotely exploitable and has a CVSS 3.1 score of 8.1 (High).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.