CVE-2026-5441 | Orthanc DICOM Server up to 1.12.10 Image Parser DicomImageDecoder.cpp DecodePsmctRle1 out-of-bounds
VulDBArchived Apr 09, 2026✓ Full text saved
A vulnerability described as problematic has been identified in Orthanc DICOM Server up to 1.12.10 . Impacted is the function DecodePsmctRle1 of the file DicomImageDecoder.cpp of the component Image Parser . The manipulation results in out-of-bounds read. This vulnerability is reported as CVE-2026-5441 . The attack can be launched remotely. No exploit exists.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-356593 · CVE-2026-5441 · GCVE-0-2026-5441
ORTHANC DICOM SERVER UP TO 1.12.10 IMAGE PARSER DICOMIMAGEDECODER.CPP DECODEPSMCTRLE1 OUT-OF-BOUNDS
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.3 $0-$5k 0.73+
Summaryinfo
A vulnerability classified as problematic has been found in Orthanc DICOM Server up to 1.12.10. The affected element is the function DecodePsmctRle1 of the file DicomImageDecoder.cpp of the component Image Parser. This manipulation causes out-of-bounds. This vulnerability appears as CVE-2026-5441. The attack may be initiated remotely. There is no available exploit.
Detailsinfo
A vulnerability has been found in Orthanc DICOM Server up to 1.12.10 and classified as problematic. Affected by this vulnerability is the function DecodePsmctRle1 of the file DicomImageDecoder.cpp of the component Image Parser. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality. The summary by CVE is:
An out-of-bounds read vulnerability exists in the `DecodePsmctRle1` function of `DicomImageDecoder.cpp`. The `PMSCT_RLE1` decompression routine, which decodes the proprietary Philips Compression format, does not properly validate escape markers placed near the end of the compressed data stream. A crafted sequence at the end of the buffer can cause the decoder to read beyond the allocated memory region and leak heap data into the rendered image output.
This vulnerability is known as CVE-2026-5441 since 04/02/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Vendor
Orthanc
Name
DICOM Server
Version
1.12.0
1.12.1
1.12.2
1.12.3
1.12.4
1.12.5
1.12.6
1.12.7
1.12.8
1.12.9
1.12.10
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/02/2026 CVE reserved
04/09/2026 +7 days Advisory disclosed
04/09/2026 +0 days VulDB entry created
04/09/2026 +0 days VulDB entry last update
Sourcesinfo
Status: Not defined
CVE: CVE-2026-5441 (🔒)
GCVE (CVE): GCVE-0-2026-5441
GCVE (VulDB): GCVE-100-356593
Entryinfo
Created: 04/09/2026 17:39
Changes: 04/09/2026 17:39 (54)
Complete: 🔍
Cache ID: 99:DD9:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸