Memory Allocation with Excessive Size Value The advisory has been revoked - it doesn't affect any version of package org.hdrhistogram:hdrhistogram (opens in a new tab)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGHDRHISTOGRAM-17821183
- published6 Jul 2026
- disclosed5 Jul 2026
- creditsara11h
Introduced: 5 Jul 2026
NewCVE-2026-14683 (opens in a new tab)Amendment
This was deemed not a vulnerability.
Overview
Affected versions of this package are vulnerable to Memory Allocation with Excessive Size Value in the decodeFromCompressedByteBuffer function due to improper handling of the lengthOfCompressedContents argument. An attacker can cause excessive memory allocation by supplying a crafted compressed byte buffer, potentially leading to application instability or denial of service.
Notes:
lengthOfCompressedContentsis read from the buffer and used directly for allocation/decompression input without bounds validation (AbstractHistogram.java2275–2283). The same unchecked length is passed on the array-backed path (line 2279).- The issue uses
allocateDirectto reach thenew byte[lengthOfCompressedContents]branch. Typical log parsing usesByteBuffer.wrap, so the heap-allocating path is not the default for.hlogingestion, though the public API allows direct buffers.