CVE-2026-97059
Received Received - Intake

Heap Over-Read in DCMTK ConcatenationLoader

Vulnerability report for CVE-2026-97059, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-24

Last updated on: 2026-09-24

Assigner: VulnCheck

Description

DCMTK through 3.7.0 contains a heap over-read vulnerability in ConcatenationLoader that copies pixel data frames without validating the PixelData buffer length against the declared NumberOfFrames. Attackers can craft malicious DICOM instances declaring more frames than the buffer contains to trigger heap over-reads that crash the application or leak adjacent heap memory.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-24
Last Modified
2026-09-24
Generated
2026-09-24
AI Q&A
2026-09-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
dcmtk dcmtk 3.7.0
dcmtk dcmtk to 3.7.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-97059 is a heap over-read vulnerability in DCMTK through version 3.7.0. It occurs in the ConcatenationLoader component when processing DICOM files. The vulnerability arises when the NumberOfFrames tag declares more frames than the actual PixelData buffer contains. This mismatch causes the software to read past the end of the allocated buffer, potentially leading to application crashes or leakage of adjacent heap memory.

Detection Guidance

To detect this vulnerability, inspect DICOM files processed by DCMTK versions before 3.7.1 for mismatches between the NumberOfFrames tag and actual PixelData buffer size. Use DCMTK tools like dcmdump to analyze DICOM headers for malformed frame declarations. Monitor application crashes or memory leaks during DICOM file processing.

Impact Analysis

This vulnerability can allow attackers to craft malicious DICOM files that trigger heap over-reads. This may cause the application to crash (denial of service) or expose sensitive memory contents. Systems processing untrusted DICOM files are at risk, particularly those in medical imaging environments where DCMTK is used for handling DICOM data.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by potentially exposing sensitive data through heap memory leaks. GDPR requires protecting personal data, and HIPAA mandates safeguarding protected health information. A heap over-read could lead to unauthorized access to adjacent memory, risking data breaches that violate these regulations.

Mitigation Strategies

Upgrade DCMTK to the latest patched version (3.7.1 or later) to address the heap over-read issue. If upgrading is not immediately possible, restrict processing of untrusted DICOM files or implement input validation to reject files declaring more frames than the PixelData buffer contains.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-97059. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart