dbcve.org
DcmtkApplication · Offis

CVE-2026-5663

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-06
Fix available
A fix is available. Upgrade to after 3.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in OFFIS DCMTK up to 3.7.0. This impacts the function executeOnReception/executeOnEndOfStudy of the file dcmnet/apps/storescp.cc of the component storescp. Performing a manipulation results in os command injection. Remote exploitation of the attack is possible. The patch is named edbb085e45788dccaf0e64d71534cfca925784b8. Applying a patch is the recommended action to fix this issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in OFFIS DCMTK storescp application (dcmnet/apps/storescp.cc). The executeOnReception and executeOnEndOfStudy functions improperly handle user input, allowing attackers to inject arbitrary OS commands. This is remotely exploitable with CVSS 9.8 critical severity.

MitigationApply the provided patch (edbb085e45788dccaf0e64d71534cfca925784b8) to implement proper input sanitization/validation on the executeOnReception and executeOnEndOfStudy function parameters, or upgrade to a patched version of DCMTK.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DcmtkApplication
Affected:<= 3.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify storescp installation
    Run 'storescp -h' or 'which storescp' to confirm the DCMTK storescp binary is present on the system
    Affected if storescp binary is found on the system
  2. Determine DCMTK version
    Run 'storescp -v' or 'dcmdump -v' to retrieve the installed DCMTK version number
    Affected if Installed version is 3.7.0 or lower
  3. Identify executeOnReception configuration
    Search configuration files and command-line arguments for 'executeOnReception' or the shorthand '-xec' to see if this feature is enabled
    Affected if executeOnReception is configured with user-controlled input
  4. Identify executeOnEndOfStudy configuration
    Search configuration files and command-line arguments for 'executeOnEndOfStudy' or the shorthand '-xest' to see if this feature is enabled
    Affected if executeOnEndOfStudy is configured with user-controlled input
  5. Inspect runtime parameters
    Review how storescp is invoked (startup scripts, systemd unit files, cron jobs) to examine all parameters passed to the executeOnReception or executeOnEndOfStudy options
    Affected if The parameters to these functions are derived from external/dicom network input without validation

A system is affected if DCMTK storescp version 3.7.0 or lower is installed AND the executeOnReception or executeOnEndOfStudy features are enabled with externally-sourced parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.7.0
Vendor patch github.com →
Interim mitigation

Apply the provided patch (edbb085e45788dccaf0e64d71534cfca925784b8) to implement proper input sanitization/validation on the executeOnReception and executeOnEndOfStudy function parameters, or upgrade to a patched version of DCMTK.

Recommended fix Moderate confidence

DCMTK 3.7.1 or later (the first release containing commit edbb085e45788dccaf0e64d71534cfca925784b8)

  1. 1. Identify the current DCMTK version in use by running 'storescp -v' or checking the package version
  2. 2. Since this is a command injection vulnerability in storescp's executeOnReception/executeOnEndOfStudy handlers, immediately restrict network exposure of the storescp service
  3. 3. If patches cannot be applied immediately, disable the executeOnReception and executeOnEndOfStudy configuration options in storescp to prevent exploitation
  4. 4. Upgrade to DCMTK version 3.7.1 or later which contains the security fix for this command injection vulnerability
  5. 5. After upgrading, verify the patch commit edbb085e45788dccaf0e64d71534cfca925784b8 is included in the new version
  6. 6. Test the storescp application to ensure normal DICOM storage functionality works correctly after upgrade
  7. 7. Re-enable network access to storescp only after confirming the upgrade is successful
Caveat Minor: Verify any custom executeOnReception/executeOnEndOfStudy scripts still function correctly after upgrade as the patch likely adds input sanitization

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dcmtk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5663 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5663 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data