# CVE-2026-82596: LatencyUtils PauseDetector LatencyStats.java LatencyStats.recordDetectedPause memory corruption

> Local attackers can trigger memory corruption in LatencyUtils via the PauseDetector component, potentially leading to code execution.

- **Severity:** Medium 4.8 (`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`)
- **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:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-m6mq-9wjq-4748

## What is CVE-2026-82596?

CVE-2026-82596 is a medium-severity memory corruption vulnerability in LatencyUtils, published on 31 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in LatencyUtils up to 2.0.3. Affected by this issue is the function LatencyStats.recordDetectedPause of the file src/main/java/org/LatencyUtils/LatencyStats.java of the component PauseDetector. Executing a manipulation can lead to memory corruption. The attack needs to be launched locally. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

No fix has been published for CVE-2026-82596 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82596 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82596 is a medium-severity memory corruption vulnerability in LatencyUtils, published on 31 Aug 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-82596 exists.

Affected product: LatencyUtils. 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-82596/ (Markdown: https://insights.sbomify.com/CVE-2026-82596/index.md)
```

## Sources

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

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