high · CVSS v3 7.5
CVE-2026-97370
CVE-2026-97370 affects the open‑source Junrar Java library, allowing a crafted RAR4 archive to trigger an infinite CPU loop during extractio
Overview
CVE-2026-97370 affects the open‑source Junrar Java library, allowing a crafted RAR4 archive to trigger an infinite CPU loop during extraction. The flaw resides in the RarVM.ExecuteCode routine, which can jump beyond the program’s code size without proper bounds checking. This results in a denial‑of‑service condition that can exhaust worker threads and degrade service availability.
Description
Junrar is an open source Java RAR archive library. Prior to 7.6.1, RarVM.ExecuteCode in src/main/java/com/github/junrar/unpack/vm/RarVM.java can repeatedly execute a VM_JMP instruction whose target is greater than or equal to the prepared program's codeSize. The setIP() function returns success without changing the instruction pointer or decrementing maxOpCount, and the jump handler continues before loop-end accounting, leaving both values unchanged. A crafted RAR4 archive can therefore keep an extraction thread in an infinite CPU loop and exhaust archive-processing worker capacity. The RAR virtual machine does not expose native process execution, so the supported impact is availability loss rather than code execution. This issue is fixed in version 7.6.1.
Impact
Defenders using Junrar for archive extraction may experience prolonged CPU usage and thread exhaustion, leading to service slowdown or unresponsiveness. The vulnerability does not enable code execution or data disclosure, but it can disrupt availability for applications that rely on Junrar. Monitoring CPU and thread metrics is essential to detect exploitation attempts.
Remediation
Upgrade Junrar to version 7.6.1 or later, where the RarVM bounds check is fixed. As an additional safeguard, configure worker thread pools with timeouts or CPU limits, and monitor for abnormal CPU spikes during archive processing. If upgrade is not immediately possible, consider sandboxing extraction or using alternative libraries.
Risk context
The CVSS v3 score of 7.5 and high severity indicate a significant risk, though no EPSS data is available. Defenders should treat this as a high‑priority issue and apply the patch promptly to avoid potential availability disruptions.
Affected products
- Junrar
Scores
- Severity
- high
- CVSS v2
- 7.8
- CVSS v3
- 7.5
- CVSS v4
- —
- EPSS
- —