Quick answers
- Is CVE-2026-14683 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14683 being exploited in the wild.
- How severe is CVE-2026-14683?
- Low severity, with a CVSS score of 3.3, published 4 July 2026.
- Which products and versions are affected?
- HdrHistogram Up to 2.2.2.
- Is there a fix for CVE-2026-14683?
- 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-14683 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-14683?
- 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 exists in HdrHistogram up to version 2.2.2 within the 'decodeFromCompressedByteBuffer' function of 'AbstractHistogram.java'. The issue stems from uncontrolled memory allocation (CWE-789/CWE-400) when processing the 'lengthOfCompressedContents' argument. A local attacker can provide a manipulated length value to force the application to allocate an excessive amount of memory, leading to an Out-of-Memory (OOM) condition and denial-of-service. While the project was notified via an issue report, no official patch has been confirmed at the time of this advisory.
Affected products
- HdrHistogram HdrHistogram Up to 2.2.2
Timeline
- 2026-07-04: disclosed: Vulnerability published via VulDB/NVD
- 2026-07-04: advisory