HdrHistogram up to 2.2.2 AbstractHistogram AbstractHistogram.java recordValueWithCount state issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 1.53+ |
Summary
A vulnerability has been found in HdrHistogram up to 2.2.2 and classified as problematic. This issue affects the function recordValueWithCount of the file src/main/java/org/HdrHistogram/AbstractHistogram.java of the component AbstractHistogram. Performing a manipulation of the argument Count results in state issue.
This vulnerability is identified as CVE-2026-14685. The attack is only possible with local access. Additionally, an exploit exists.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability classified as problematic has been found in HdrHistogram up to 2.2.2. This affects the function recordValueWithCount of the file src/main/java/org/HdrHistogram/AbstractHistogram.java of the component AbstractHistogram. The manipulation of the argument count with an unknown input leads to a state issue vulnerability. CWE is classifying the issue as CWE-371. This is going to have an impact on integrity.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-14685. The exploitability is told to be easy. An attack has to be approached locally. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: State issueCWE: CWE-371
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/04/2026 Advisory disclosed07/04/2026 VulDB entry created
07/04/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 221
Status: Not defined
CVE: CVE-2026-14685 (🔒)
GCVE (CVE): GCVE-0-2026-14685
GCVE (VulDB): GCVE-100-376281
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/04/2026 06:45Changes: 07/04/2026 06:45 (58)
Complete: 🔍
Submitter: sara11h
Cache ID: 216::103
Submit
Accepted
- Submit #846761: HdrHistogram 2.2.2 and earlier Improper Input Validation (by sara11h)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.