# CVE-2026-14685: HdrHistogram AbstractHistogram AbstractHistogram.java recordValueWithCount state issue

> A disputed state issue in HdrHistogram's recordValueWithCount function may allow local attackers to manipulate internal state, though security boundary violations are unconfirmed.

- **Severity:** Medium 4.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-14685, GHSA-j3mx-fh6g-v48r, UBUNTU-CVE-2026-14685

## What is CVE-2026-14685?

CVE-2026-14685 is a medium-severity vulnerability in HdrHistogram, published on 4 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in HdrHistogram up to 2.2.2. This vulnerability affects the function recordValueWithCount of the file src/main/java/org/HdrHistogram/AbstractHistogram.java of the component AbstractHistogram. Such manipulation of the argument Count leads to state issue. The attack can only be performed from a local environment. The exploit has been disclosed to the public and may be used. The existence of this vulnerability is still disputed at present. This issue is disputed due to the potential lack of crossing of security boundaries and the pre-requisites for a successful attack.

Weakness: CWE-371

## Which versions are affected by CVE-2026-14685?


## How do I fix CVE-2026-14685?

No fix published yet.

## Is CVE-2026-14685 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14685 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14685 and fix it if it is affected.

What it is: CVE-2026-14685 is a medium-severity vulnerability in HdrHistogram, published on 4 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14685 exists.

Affected product: HdrHistogram. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14685/ (Markdown: https://insights.sbomify.com/CVE-2026-14685/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14685
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14685
- OSV: https://osv.dev/vulnerability/CVE-2026-14685

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14685/
Summaries are generated and may contain mistakes; the official description above is the record.