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.
Metrics
Affected Vendors & Products
References
History
Wed, 15 Apr 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-400 CWE-789 |
Tue, 14 Apr 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Orthanc-server
Orthanc-server orthanc |
|
| Weaknesses | CWE-770 | |
| CPEs | cpe:2.3:a:orthanc-server:orthanc:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Orthanc-server
Orthanc-server orthanc |
Tue, 14 Apr 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Fri, 10 Apr 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-400 CWE-789 |
Fri, 10 Apr 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Orthanc
Orthanc dicom Server |
|
| Vendors & Products |
Orthanc
Orthanc dicom Server |
Thu, 09 Apr 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Memory Exhaustion via Unbounded Content-Length | |
| References |
|
Status: PUBLISHED
Assigner: certcc
Published: 2026-04-09T14:43:55.684Z
Updated: 2026-04-14T16:34:31.991Z
Reserved: 2026-04-02T19:22:26.410Z
Link: CVE-2026-5440
Updated: 2026-04-14T15:12:41.250Z
Status : Analyzed
Published: 2026-04-09T15:16:16.337
Modified: 2026-04-14T20:26:57.417
Link: CVE-2026-5440
No data.