dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10194

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 weakness has been identified in OFFIS DCMTK 3.7.0. This affects the function DcmQueryRetrieveIndexDatabaseHandle::deleteOldestImages of the file dcmqrdb/libsrc/dcmqrdbi.cc of the component dcmqrscp. Executing a manipulation can lead to heap-based buffer overflow. The attack may be launched remotely. This patch is called 0f78a4ef6f645ea5530166e445e5436a5de58e75. A patch should be applied to remediate 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 · moderate confidence

Heap-based buffer overflow in the deleteOldestImages function of dcmqrscp (DICOM query/retrieve service class provider) in DCMTK 3.7.0. The vulnerability exists in dcmqrdb/libsrc/dcmqrdbi.cc and can be exploited remotely to potentially execute arbitrary code or cause denial of service through memory corruption.

MitigationApply patch commit 0f78a4ef6f645ea5530166e445e5436a5de58e75 to fix the buffer overflow in DcmQueryRetrieveIndexDatabaseHandle::deleteOldestImages; ensure input validation and bounds checking are enforced.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify DCMTK installation and version
    Run 'dcmqrscp -v' or 'dcmtk-version' to get the DCMTK version. Alternatively, check package manager for installed DCMTK packages.
    Affected if The installed version is DCMTK 3.7.0 (exact match to affected version). Versions prior to the patch commit are also likely affected.
  2. Locate the dcmqrscp binary
    Run 'which dcmqrscp' or search for the binary in common paths like /usr/bin/dcmqrscp or /usr/local/bin/dcmqrscp.
    Affected if The dcmqrscp binary exists on the system, indicating the vulnerable component is present.
  3. Verify if query/retrieve service is configured or running
    Check running processes for 'dcmqrscp' via 'ps aux | grep dcmqrscp' and check for configuration files (often named dcmqrscp.cfg) in /etc, /usr/local/etc, or application directories.
    Affected if The dcmqrscp service is actively running or configured to run, enabling the vulnerable code path.
  4. Inspect DICOM query/retrieve service configuration
    Examine the dcmqrscp configuration file for enabled storage areas and query/retrieve AE titles. Check if network listeners are bound to accessible interfaces.
    Affected if The query/retrieve service is bound to network interfaces and accepts external connections, exposing the vulnerability to remote attackers.

A system is affected if it runs DCMTK version 3.7.0 with the dcmqrscp query/retrieve service enabled and exposed to network traffic.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply patch commit 0f78a4ef6f645ea5530166e445e5436a5de58e75 to fix the buffer overflow in DcmQueryRetrieveIndexDatabaseHandle::deleteOldestImages; ensure input validation and bounds checking are enforced.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10194 — 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-10194 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