Skip to main content
VulnerabilityPublished Updated

CVE-2026-14686: HdrHistogram · Incorrect Comparison

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.3% chance of exploitation in 30 days – higher than 25% 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:L/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 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 17 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

Monitor vendor communications for updates on remediation.

Description

A vulnerability was found in HdrHistogram up to 2.2.2. This issue affects the function org.HdrHistogram.DoubleHistogram.recordValue of the file src/main/java/org/HdrHistogram/DoubleHistogram.java of the component Range Check. Performing a manipulation results in incorrect comparison. The attack is only possible with local access. The exploit has been made public and could be used. The presence of this vulnerability remains uncertain at this time. 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…