Skip to main content
Vulnerability Database/CVE-2026-44031

CVE-2026-44031: OFFIS DCMTK DoS Vulnerability

CVE-2026-44031 is a denial of service flaw in OFFIS DCMTK that allows unauthenticated attackers to crash services via deeply nested DICOM datasets. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-44031 Overview

CVE-2026-44031 is an uncontrolled recursion vulnerability [CWE-674] in the DcmSequenceOfItems::read() and DcmItem::read() functions within the dcmdata library of OFFIS DCMTK 3.7.0. A remote, unauthenticated attacker can trigger stack exhaustion and crash the process by sending a Digital Imaging and Communications in Medicine (DICOM) dataset containing deeply nested sequence (SQ) elements. The affected parsing occurs before any authentication, exposing network-facing DICOM services such as storescp, dcmrecv, and dcmqrscp. Local tools including dcmdump also crash when opening a malicious file. The issue is fixed in commit 885ff0f10372bd589b5f44cea974f28a3964cb0f, which introduces a configurable sequence nesting depth limit defaulting to 64.

Critical Impact

Pre-authentication denial of service against DICOM services used in medical imaging infrastructure, achievable via a single crafted C-STORE request.

Affected Products

  • OFFIS DCMTK 3.7.0 (dcmdata library)
  • DICOM services built on DCMTK: storescp, dcmrecv, dcmqrscp
  • Local DCMTK utilities such as dcmdump

Discovery Timeline

  • 2026-10-08 - CVE-2026-44031 published to the National Vulnerability Database (NVD)
  • 2026-10-08 - Last updated in NVD database

Technical Details for CVE-2026-44031

Vulnerability Analysis

The vulnerability resides in DCMTK's DICOM dataset parser. DICOM encodes complex structures using Sequence of Items (SQ) value representations, where each item can itself contain further sequences. When parsing these constructs, DcmSequenceOfItems::read() and DcmItem::read() recursively call each other for every nested sequence level. The implementation does not enforce a depth limit, so an attacker can craft a dataset with thousands of nested SQ elements that consume the call stack until the process crashes.

Because the parser executes against the received byte stream before any association-level authentication is validated, the crash occurs on any DCMTK-based DICOM service that accepts incoming C-STORE requests. The result is a reliable, remote, pre-authentication denial of service against medical imaging servers, PACS components, and research tooling that embed DCMTK.

Root Cause

The root cause is unbounded mutual recursion between DcmSequenceOfItems::read() and DcmItem::read() during DICOM dataset parsing. Each nested SQ element pushes a new frame onto the call stack, and no counter or ceiling constrains how deep the recursion may proceed. Real-world DICOM data rarely exceeds 5–10 nesting levels, but the parser accepted arbitrary depth, allowing stack exhaustion.

Attack Vector

An attacker sends a DICOM dataset containing deeply nested sequences to a DCMTK-based service listener over the network, typically via a C-STORE request. No credentials or user interaction are required. For local tools such as dcmdump, the same crash occurs when the operator opens a malicious .dcm file supplied by the attacker.

c
/*
 *
- *  Copyright (C) 1994-2025, OFFIS e.V.
+ *  Copyright (C) 1994-2026, OFFIS e.V.
 *  All rights reserved.  See COPYRIGHT file for details.
 *
 *  This software and supporting documentation were developed by
*/
// Source: https://github.com/DCMTK/dcmtk/commit/885ff0f10372bd589b5f44cea974f28a3964cb0f

Detection Methods for CVE-2026-44031

Indicators of Compromise

  • Unexpected crashes or restarts of storescp, dcmrecv, dcmqrscp, or other DCMTK-based listeners.
  • Core dumps or stack-overflow signatures (SIGSEGV with exhausted stack) in DICOM service process logs.
  • Inbound DICOM associations from untrusted peers immediately preceding service termination.

Detection Strategies

  • Inspect received DICOM datasets for abnormally deep SQ element nesting (greater than 10 levels) before passing them to the parser.
  • Monitor DICOM service availability and alert on repeated process restarts within short time windows.
  • Correlate network captures on DICOM ports (default 104, 11112) with service crash events to identify malicious datasets.

Monitoring Recommendations

  • Enable process supervision for DCMTK listeners and forward crash telemetry to a centralized logging platform.
  • Capture full packet data on DICOM traffic from external or semi-trusted networks for post-incident analysis.
  • Track connection patterns from new or unexpected Application Entity (AE) titles.

How to Mitigate CVE-2026-44031

Immediate Actions Required

  • Apply upstream commit 885ff0f10372bd589b5f44cea974f28a3964cb0f or upgrade to a DCMTK release that includes the fix.
  • Restrict network access to DCMTK-based DICOM services so that only trusted modalities and PACS peers can initiate associations.
  • Audit all internal tooling and third-party products that embed DCMTK 3.7.0 and schedule rebuilds against the patched library.

Patch Information

The fix is provided in DCMTK commit 885ff0f10372bd589b5f44cea974f28a3964cb0f, which adds a configurable sequence nesting depth limit (default 64). The limit can be adjusted at compile time via the DCMTK_MAX_SEQUENCE_NESTING macro, or at runtime through DcmInputStream::setMaxNestingDepth(), DcmItem::setMaxNestingDepth(), and DcmFileFormat::setMaxNestingDepth(). Setting the runtime value to -1 disables the check. See the DCMTK commit 885ff0f and DCMTK Issue #1191 for full technical details.

Workarounds

  • Place DCMTK-based services behind a DICOM-aware proxy or firewall that filters datasets with excessive SQ nesting depth.
  • Limit network exposure to known AE titles and source IP addresses, blocking unsolicited associations from the internet.
  • Run DCMTK services under a process supervisor with automatic restart to limit the duration of a successful DoS condition.
bash
# Build DCMTK with a stricter compile-time sequence nesting limit
cmake -DCMAKE_CXX_FLAGS="-DDCMTK_MAX_SEQUENCE_NESTING=32" ..
make && make install

# Or set the limit at runtime in application code (default is 64)
# DcmFileFormat::setMaxNestingDepth(32);

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.