Authenticated memory corruption via unbounded image indexing
Published May 31, 2026 · Updated May 31, 2026
Heap-based buffer overflow in OFFIS DCMTK 3.7.0 dcmqrscp allows remote authenticated users to corrupt process memory. During quota-driven deletion, deleteOldestImages appends matching index records to StudyArray while incrementing nbimages without enforcing MAX_NUMBER_OF_IMAGES. DICOM peer access and quota-triggered deletion are required; public sources confirm memory corruption but not code execution.
Summary
What happened
Heap-based buffer overflow in OFFIS DCMTK 3.7.0 dcmqrscp allows remote authenticated users to corrupt process memory. During quota-driven deletion, deleteOldestImages appends matching index records to StudyArray while incrementing nbimages without enforcing MAX_NUMBER_OF_IMAGES. DICOM peer access and quota-triggered deletion are required; public sources confirm memory corruption but not code execution.
The record
- CVE
- CVE-2026-10194
- Published
- May 31, 2026
- Updated
- May 31, 2026
- Vendor
- OFFIS e.V.
- Product
- DCMTK
- Classifications
- CWE-119, CWE-122, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 31, 2026CVE publishedPublication date reported by the CVE source.
- May 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.7.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo