Skip to main content
VulnerabilityPublished Updated

CVE-2026-97059: OFFIS DCMTK · Out-of-bounds Read

Affects OFFIS DCMTKSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
OFFISDCMTKAffected
  • <=3.7.0
Fixed in–
GitHubdcmtk/dcmtkpkg:github/dcmtk/dcmtkOther threatsAffected
  • <=3.7.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, avoid processing untrusted DICOM files or apply application-level controls to limit exposure.

Description

DCMTK versions up to 3.7.0 have a heap over-read vulnerability in the ConcatenationLoader component. This occurs when pixel data frames are copied without validating the PixelData buffer length against the declared NumberOfFrames. Maliciously crafted DICOM files can trigger heap over-reads, potentially causing application crashes or leaking adjacent heap memory.

References

Community reviews

Loading reviews…