CVE-2026-5663
OS Command Injection in OFFIS DCMTK storescp Enables Remote Exploitation
Publication date: 2026-04-06
Last updated on: 2026-04-27
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| offis | dcmtk | to 3.7.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-77 | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain specific information about how CVE-2026-5663 affects compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
CVE-2026-5663 is a security vulnerability in the OFFIS DCMTK software up to version 3.7.0, specifically in the storescp component's executeOnReception and executeOnEndOfStudy functions. The flaw allows an attacker to perform OS command injection by manipulating certain input fields.
The vulnerability arises because certain text fields from incoming DICOM data—such as Study Instance UID, SOP Instance UID, Patient's Name, and the calling SCU's network presentation address—are not properly sanitized before being used in shell command executions. This can allow special characters in these fields to be interpreted as shell escape sequences, enabling remote attackers to inject and execute arbitrary commands on the system.
The issue is mitigated by a patch that sanitizes these input strings using a whitelist approach, replacing disallowed characters with underscores and enclosing some strings in quotes to prevent shell injection.
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to execute arbitrary operating system commands on a system running the vulnerable DCMTK storescp component. This could lead to unauthorized access, data manipulation, or disruption of services.
Because the attack can be performed remotely without authentication, it poses a significant risk to systems processing DICOM data, potentially compromising the confidentiality, integrity, and availability of medical imaging data and related infrastructure.
What immediate steps should I take to mitigate this vulnerability?
The recommended immediate step to mitigate this vulnerability is to apply the patch identified by commit edbb085e45788dccaf0e64d71534cfca925784b8.
This patch sanitizes all input strings from DICOM fields and network parameters before they are used in command execution contexts, preventing command injection.
Applying this patch ensures that unsafe characters are replaced or removed, and commands executed by the storescp component are safe from injection attacks.