CVE-2026-10194
Heap-based Buffer Overflow in OFFIS DCMTK
Publication date: 2026-05-31
Last updated on: 2026-05-31
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| offis | dcmtk | 3.7.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a weakness found in OFFIS DCMTK version 3.7.0, specifically in the function DcmQueryRetrieveIndexDatabaseHandle::deleteOldestImages within the dcmqrscp component. It allows an attacker to cause a heap-based buffer overflow by manipulating this function. The vulnerability can be exploited remotely.
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to a heap-based buffer overflow, which may allow an attacker to execute arbitrary code, cause a denial of service, or crash the affected system. Since the attack can be launched remotely, it poses a significant risk to systems using the vulnerable DCMTK version without the patch.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should apply the patch identified by commit 0f78a4ef6f645ea5530166e445e5436a5de58e75 to your OFFIS DCMTK 3.7.0 installation.
This patch fixes the remote heap buffer overflow in the dcmqrscp component, specifically in the function DcmQueryRetrieveIndexDatabaseHandle::deleteOldestImages.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.