Skip to main content
VulnerabilityPublished Updated

CVE-2026-14683: HdrHistogram · Uncontrolled Memory Allocation

Affects HdrHistogramSource CVE Database V5

0
Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
HdrHistogramAffected
  • =2.2.0
  • =2.2.1
  • =2.2.2
Fixed in–
Mavenorg.hdrhistogram/HdrHistogrampkg:maven/org.hdrhistogram/HdrHistogramOther threatsAffected
  • =2.2.0
  • =2.2.1
  • =2.2.2
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:hdrhistogram:hdrhistogram:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the local access requirement and disputed nature, no immediate urgent action is mandated.

Description

A vulnerability was detected in HdrHistogram up to 2.2.2. Affected by this issue is the function org.HdrHistogram.AbstractHistogram.decodeFromCompressedByteBuffer of the file src/main/java/org/HdrHistogram/AbstractHistogram.java. The manipulation of the argument lengthOfCompressedContents results in uncontrolled memory allocation. The attack needs to be approached locally. The exploit is now public and may be used. It is still unclear if this vulnerability genuinely exists. This issue is disputed due to the potential lack of crossing of security boundaries and the pre-requisites for a successful attack.

References

Community reviews

Loading reviews…