Application crash via PixelData fragment length underflow
Published Dec 12, 2025 · Updated Dec 12, 2025
Out-of-bounds write in GDCM 3.0.24 and earlier allows attackers to crash an application by opening a malformed DICOM file. SequenceOfFragments::ReadValue indexes three bytes before the final PixelData fragment without first ensuring that its length is at least three, causing unsigned underflow. The same embedded GDCM path affects SimpleITK 2.5.2 and earlier and medInria 4.0 and earlier; file opening is required, and the reported result is a process crash.
Summary
What happened
Out-of-bounds write in GDCM 3.0.24 and earlier allows attackers to crash an application by opening a malformed DICOM file. SequenceOfFragments::ReadValue indexes three bytes before the final PixelData fragment without first ensuring that its length is at least three, causing unsigned underflow. The same embedded GDCM path affects SimpleITK 2.5.2 and earlier and medInria 4.0 and earlier; file opening is required, and the reported result is a process crash.
The record
- CVE
- CVE-2025-11266
- Published
- Dec 12, 2025
- Updated
- Dec 12, 2025
- Vendor
- Insight Software Consortium
- Product
- SimpleITK
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2025CVE publishedPublication date reported by the CVE source.
- Dec 12, 2025Record 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=0 <=2.5.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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