Bug 2526089 (CVE-2026-82596)

Summary: CVE-2026-82596 org.latencyutils/latencyutils: LatencyUtils: Memory corruption via local manipulation
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: abrianik, ant, anujha, aschwart, asoldano, aszczucz, bbaranow, bmaxwell, boliveir, bstansbe, ccranfor, cescoffi, cmah, dhanak, dlofthou, drichtar, drosa, dsimansk, ewittman, fmongiar, ggrzybek, gmalinko, gsmet, gtanzill, istudens, ivassile, iweiss, janstey, jbuscemi, jmartisk, jnethert, jpechane, jraez, kaycoth, kingland, manderse, mnovotny, mosmerov, mposolda, msvehla, nipatil, nwallace, olubyans, ozzy, pantinor, parichar, pberan, pdelbell, pesilva, pjindal, pmackay, rguimara, rkubis, rmartinc, rstancel, rstepani, sausingh, sbiarozk, sdawley, ssilvert, sthorger, tasato, thjenkin, varjain, vdosoudi, vmuzikar
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in LatencyUtils. A local attacker can exploit this vulnerability by performing a manipulation within the `PauseDetector` component, specifically affecting the `LatencyStats.recordDetectedPause` function. This can lead to memory corruption, potentially impacting the stability and integrity of the system.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-08-31 00:11:26 UTC 
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.