LatencyUtils up to 2.0.3 PauseDetector LatencyStats.java LatencyStats.recordDetectedPause memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 1.46+ |
Summary
A vulnerability identified as critical has been detected in LatencyUtils up to 2.0.3. This affects the function LatencyStats.recordDetectedPause of the file src/main/java/org/LatencyUtils/LatencyStats.java of the component PauseDetector. The manipulation leads to memory corruption.
This vulnerability is documented as CVE-2026-82596. The attack needs to be performed locally. Additionally, an exploit exists.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability, which was classified as problematic, has been found in LatencyUtils up to 2.0.3. This issue affects the function LatencyStats.recordDetectedPause of the file src/main/java/org/LatencyUtils/LatencyStats.java of the component PauseDetector. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is availability.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-82596. The exploitation is known to be easy. Attacking locally is a requirement. Technical details as well as a public exploit are known.
The exploit is available 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.
Statistical analysis made it clear that VulDB provides the best quality for 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: Memory corruptionCWE: CWE-119
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
08/30/2026 Advisory disclosed08/30/2026 VulDB entry created
08/30/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 22
Status: Not defined
CVE: CVE-2026-82596 (🔒)
GCVE (CVE): GCVE-0-2026-82596
GCVE (VulDB): GCVE-100-397091
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/30/2026 08:30Changes: 08/30/2026 08:30 (58)
Complete: 🔍
Submitter: Yu Bao from PayPal Cyber Security Team
Cache ID: 216::103
Submit
Accepted
- Submit #892660: LatencyUtils 2.0.3 PauseDetector DOS (by Yu Bao from PayPal Cyber Security Team)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.