Process crash via named-pipe heap overflow
Published Jun 21, 2026 · Updated Jun 21, 2026
Heap-based buffer overflow in OFFIS DCMTK 3.0 through 3.7.0 allows local users to crash XML-processing applications via a named pipe. XMLNode::parseFile treats ftell returning -1 as a valid length, allocates three heap bytes, and passes a size_t-converted -1 to fread. A local user must supply the FIFO to an application that invokes this parser; the demonstrated consequence is a process crash.
Summary
What happened
Heap-based buffer overflow in OFFIS DCMTK 3.0 through 3.7.0 allows local users to crash XML-processing applications via a named pipe. XMLNode::parseFile treats ftell returning -1 as a valid length, allocates three heap bytes, and passes a size_t-converted -1 to fread. A local user must supply the FIFO to an application that invokes this parser; the demonstrated consequence is a process crash.
The record
- CVE
- CVE-2026-12805
- Published
- Jun 21, 2026
- Updated
- Jun 21, 2026
- Vendor
- OFFIS e.V.
- Product
- DCMTK
- Classifications
- CWE-119, CWE-122
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 21, 2026CVE publishedPublication date reported by the CVE source.
- Jun 21, 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.0
- Affected versionversion=3.1
- Affected versionversion=3.2
- Affected versionversion=3.3
- Affected versionversion=3.4
- Affected versionversion=3.5
- Affected versionversion=3.6
- 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
- DCMTK Vulnerability Report FIFO reproducerproof of concept · unverified
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