Memory corruption via overflowed PAM buffer size
Published Apr 9, 2026 · Updated Apr 9, 2026
Heap buffer overflow in Orthanc 1.12.10 and earlier allows attackers to corrupt memory through a crafted PAM image embedded in a DICOM file. The PAM parser multiplies attacker-controlled image dimensions with 32-bit unsigned arithmetic, allocates the wrapped small buffer, then writes the full pixel data beyond it. Orthanc must process the crafted file; the resulting memory corruption can crash the server, while arbitrary code execution is not established for this flaw.
Summary
What happened
Heap buffer overflow in Orthanc 1.12.10 and earlier allows attackers to corrupt memory through a crafted PAM image embedded in a DICOM file. The PAM parser multiplies attacker-controlled image dimensions with 32-bit unsigned arithmetic, allocates the wrapped small buffer, then writes the full pixel data beyond it. Orthanc must process the crafted file; the resulting memory corruption can crash the server, while arbitrary code execution is not established for this flaw.
The record
- CVE
- CVE-2026-5444
- Published
- Apr 9, 2026
- Updated
- Apr 9, 2026
- Vendor
- Orthanc
- Product
- Orthanc
- Classifications
- CWE-787, CWE-190, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2026CVE publishedPublication date reported by the CVE source.
- Apr 9, 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=0 <=1.12.10
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.
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