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-17821182
- published6 Jul 2026
- disclosed4 Jul 2026
- creditsara11h
Introduced: 4 Jul 2026
NewCVE-2026-14684 (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 decodeFromByteBuffer function due to improper handling of the numberOfSignificantValueDigits argument. An attacker can cause excessive memory consumption by supplying crafted input.
Notes:
- The issue describes parameters “from Untrusted Buffer,” but the PoC never decodes a buffer. It invokes the public constructor directly, which does not prove the decode API is exploitable end-to-end as claimed.
- The library does pass decoded header parameters into a constructor without an explicit memory budget check, which could allow moderate allocation pressure if an application decodes untrusted histogram bytes.
- That is a narrower, lower-severity concern than the submitted OOM-DoS narrative, and it remains undemonstrated by this PoC.