A gzip decompression bomb vulnerability exists when Orthanc processes HTTP request with `Content-Encoding: gzip`. The server does not enforce limits on decompressed size and allocates memory based on attacker-controlled compression metadata. A specially crafted gzip payload can trigger excessive memory allocation and exhaust system memory.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
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 gzip decompression bomb vulnerability exists when Orthanc processes HTTP request with `Content-Encoding: gzip`. The server does not enforce limits on decompressed size and allocates memory based on attacker-controlled compression metadata. A specially crafted gzip payload can trigger excessive memory allocation and exhaust system memory. | |
| Title | Gzip Decompression Bomb via Content-Encoding Header | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: certcc
Published:
Updated: 2026-04-09T14:44:05.375Z
Reserved: 2026-04-02T19:21:58.543Z
Link: CVE-2026-5438
No data.
Status : Received
Published: 2026-04-09T15:16:15.327
Modified: 2026-04-09T15:16:15.327
Link: CVE-2026-5438
No data.
OpenCVE Enrichment
Updated: 2026-04-10T08:53:23Z
Weaknesses
No weakness.