# CVE-2026-10194: OFFIS DCMTK dcmqrscp dcmqrdbi.cc deleteOldestImages heap-based overflow

> Remote attackers can trigger a heap-based buffer overflow in DCMTK's dcmqrscp component, potentially leading to code execution or denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 May 2026
- **Updated:** 3 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-10194, GHSA-x58f-wmvg-jxpc, UBUNTU-CVE-2026-10194

## What is CVE-2026-10194?

CVE-2026-10194 is a medium-severity memory corruption vulnerability in OFFIS DCMTK, published on 31 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-10194?


## How do I fix CVE-2026-10194?

Apply the vendor's patch.

## Is CVE-2026-10194 being exploited?

There is no known exploitation of CVE-2026-10194 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10194 and fix it if it is affected.

What it is: CVE-2026-10194 is a medium-severity memory corruption vulnerability in OFFIS DCMTK, published on 31 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10194 in the wild and no public exploit code.

Affected product: OFFIS DCMTK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10194/ (Markdown: https://insights.sbomify.com/CVE-2026-10194/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10194
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10194
- OSV: https://osv.dev/vulnerability/CVE-2026-10194

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10194/
Summaries are generated and may contain mistakes; the official description above is the record.