Quick answers
- Is CVE-2026-14684 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14684 being exploited in the wild.
- How severe is CVE-2026-14684?
- Low severity, with a CVSS score of 3.3, published 5 July 2026.
- Which products and versions are affected?
- HdrHistogram Up to 2.2.2.
- Is there a fix for CVE-2026-14684?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-14684 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-14684?
- Check whether you run HdrHistogram at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability classified as CWE-789 (Memory Allocation with Excessive Size Value) and CWE-400 (Uncontrolled Resource Consumption) exists in HdrHistogram up to version 2.2.2. The flaw is located in the `org.HdrHistogram.AbstractHistogram.decodeFromByteBuffer` function within `src/main/java/org/HdrHistogram/AbstractHistogram.java`. By manipulating the `numberOfSignificantValueDigits` argument in a serialized buffer, a local attacker can trigger an Out-of-Memory (OOM) condition. While an exploit has been published, the project has not yet released a formal patch at the time of reporting. The attack requires local access and low privileges.
Affected products
- HdrHistogram HdrHistogram Up to 2.2.2
Timeline
- 2026-07-05: advisory: NVD publication date
- 2026-07-05: disclosed: Public disclosure of the vulnerability and exploit