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.
CVE-2026-97059
Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-09-24. a secondary CVSS source baseline 8.2; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(high)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 24, 2026
Last Modified
September 24, 2026
Advisory Details (7)
Auto-updated Sep 24, 2026DCMTK through 3.7.0 Heap Over-read via NumberOfFrames | Advisories | VulnCheck
https://www.vulncheck.com/advisories/dcmtk-through-3.7.0-heap-over-read-via-numberofframesdcmtk/dcmfg/libsrc/concatenationloader.cc at ccfd10b84ff3c9a40b7b331698aedf06d421fc43 · DCMTK/dcmtk · GitHub
https://github.com/DCMTK/dcmtk/blob/ccfd10b84ff3c9a40b7b331698aedf06d421fc43/dcmfg/libsrc/concatenationloader.cc#L399-L430dcmtk/dcmfg/libsrc/concatenationloader.cc at ccfd10b84ff3c9a40b7b331698aedf06d421fc43 · DCMTK/dcmtk · GitHub
https://github.com/DCMTK/dcmtk/blob/ccfd10b84ff3c9a40b7b331698aedf06d421fc43/dcmfg/libsrc/concatenationloader.cc#L334-L360commit c33790827a19 (DCMTK/dcmtk)
Patch available: DCMTK/dcmtk latest (contains commit c33790827a19)
https://github.com/DCMTK/dcmtk/commit/c33790827a192a598d20463af701a8b819f46ec1commit 18379d5b8d23 (DCMTK/dcmtk)
Patch available: DCMTK/dcmtk latest (contains commit 18379d5b8d23)
https://github.com/DCMTK/dcmtk/commit/18379d5b8d234977cc30644e9e70d76d89c87285Vendor Advisories for CVE-2026-97059(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-25 08:36 UTCGHSA enrichment
- 2026-09-24 21:01 UTCEG score recompute
- 2026-09-24 21:01 UTCGHSA enrichment
- 2026-09-24 14:33 UTCEG score recompute
- 2026-09-24 13:54 UTCEG score recompute
- 2026-09-24 13:53 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-97059?
When was CVE-2026-97059 disclosed?
What is the CVSS score of CVE-2026-97059?
How do I remediate CVE-2026-97059?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-97059
Is Your Infrastructure Affected by CVE-2026-97059?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.