CVE-2026-82596

LOWPre-NVD 3.33.3—
EchelonGraph scoreHIGH confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-08-31. a secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.3
EG Score
3.3(high)
EG Risk
31(Track)
EG Risk 31/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity33% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 31, 2026

Last Modified

August 31, 2026

References (6)

Vendor Advisories for CVE-2026-82596(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 14:04 UTCEPSS rescore
  2. 2026-09-23 20:04 UTCEG score recompute
  3. 2026-09-23 20:04 UTCGHSA enrichment
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 16:01 UTCEPSS rescore
  6. 2026-09-21 21:09 UTCEPSS rescore
  7. 2026-09-20 20:16 UTCEPSS rescore
  8. 2026-09-20 13:25 UTCEG score recompute
  9. 2026-09-20 13:25 UTCGHSA enrichment
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-17 06:47 UTCEG score recompute
  12. 2026-09-17 06:47 UTCGHSA enrichment
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-13 23:40 UTCEG score recompute
  18. 2026-09-13 23:40 UTCGHSA enrichment
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-10 17:01 UTCEG score recompute
  22. 2026-09-10 17:01 UTCGHSA enrichment
  23. 2026-09-08 22:01 UTCEPSS rescore
  24. 2026-09-07 10:23 UTCEG score recompute
  25. 2026-09-07 10:23 UTCGHSA enrichment
Show 19 more
  1. 2026-09-06 13:48 UTCEPSS rescore
  2. 2026-09-05 15:31 UTCEPSS rescore
  3. 2026-09-04 03:42 UTCEG score recompute
  4. 2026-09-04 03:42 UTCGHSA enrichment
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-31 21:03 UTCEG score recompute
  9. 2026-08-31 21:03 UTCGHSA enrichment
  10. 2026-08-31 18:26 UTCEG score recompute
  11. 2026-08-31 18:26 UTCGHSA enrichment
  12. 2026-08-31 18:20 UTCNVD updateCVSS v4 → 1.9
  13. 2026-08-31 17:50 UTCEG score recompute
  14. 2026-08-31 17:50 UTCGHSA enrichment
  15. 2026-08-31 17:49 UTCMITRE cvelistV5CVSS v4 → 4.8
  16. 2026-08-31 00:19 UTCEG score recompute
  17. 2026-08-31 00:19 UTCNVD updateCVSS v4 → 1.9
  18. 2026-08-31 00:05 UTCEG score recompute
  19. 2026-08-31 00:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82596?
CVE-2026-82596 is a low vulnerability published on August 31, 2026. 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…
When was CVE-2026-82596 disclosed?
CVE-2026-82596 was first published in the National Vulnerability Database on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82596 actively exploited?
CVE-2026-82596 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.6% of all scored CVEs.
What is the CVSS score of CVE-2026-82596?
CVE-2026-82596 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-82596?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82596, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82596

Explore →

Is Your Infrastructure Affected by CVE-2026-82596?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs