CVE-2026-5440 | Orthanc DICOM Server up to 1.12.10 HTTP Content-Length allocation of resources

VDB-356590 · CVE-2026-5440 · GCVE-0-2026-5440 ORTHANC DICOM SERVER UP TO 1.12.10 HTTP CONTENT-LENGTH ALLOCATION OF RESOURCES HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.3 $0-$5k 0.73+ Summaryinfo A vulnerability labeled as problematic has been found in Orthanc DICOM Server up to 1.12.10. This vulnerability affects unknown code of the component HTTP Handler. Executing a manipulation of the argument Content-Length can lead to allocation of resources. This vulnerability is registered as CVE-2026-5440. It is possible to launch the attack remotely. No exploit is available. Detailsinfo A vulnerability classified as problematic was found in Orthanc DICOM Server up to 1.12.10. This vulnerability affects an unknown part of the component HTTP Handler. The manipulation of the argument Content-Length with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect availability. CVE summarizes: A memory exhaustion vulnerability exists in the HTTP server due to unbounded use of the `Content-Length` header. The server allocates memory directly based on the attacker supplied header value without enforcing an upper limit. A crafted HTTP request containing an extremely large `Content-Length` value can trigger excessive memory allocation and server termination, even without sending a request body. This vulnerability was named CVE-2026-5440 since 04/02/2026. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project. 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: Allocation of resources CWE: CWE-770 / CWE-400 / CWE-404 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-5440 (🔒) GCVE (CVE): GCVE-0-2026-5440 GCVE (VulDB): GCVE-100-356590 Entryinfo Created: 04/09/2026 17:39 Changes: 04/09/2026 17:39 (52) Complete: 🔍 Cache ID: 99:814:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸