Is CVE-2026-97370 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-97370 being exploited in the wild.

How severe is CVE-2026-97370?

High severity, with a CVSS score of 7.5, published 15 October 2026.

Which products and versions are affected?

com.github.junrar:junrar (Maven) <= 7.6.0, ECOSYSTEM:introduced=0,fixed=7.6.1.

Is there a fix for CVE-2026-97370?

Yes. com.github.junrar:junrar (Maven): upgrade to 7.6.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-97370 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-97370?

Check whether you run Junrar or com.github.junrar:junrar (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-97370: Junrar RarVM infinite loop in RAR4 extraction

Q: Is there a fix for CVE-2026-97370?

Yes. com.github.junrar:junrar (Maven): upgrade to 7.6.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-97370 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-97370?

Check whether you run Junrar or com.github.junrar:junrar (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-97370 · Severity: high · CVSS 7.5 · Published 2026-10-15

Junrar is a library for extracting RAR archives. A malicious RAR4 archive can trigger an infinite CPU loop in the virtual machine that Junrar uses to decompress data, permanently freezing the extraction process. Attackers can use this to exhaust server capacity by repeatedly submitting crafted archives for processing.

Technologies: com.github.junrar:junrar (Maven). Vendors: Maven.

Quick answers

Is CVE-2026-97370 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-97370 being exploited in the wild.
How severe is CVE-2026-97370?: High severity, with a CVSS score of 7.5, published 15 October 2026.
Which products and versions are affected?: com.github.junrar:junrar (Maven) <= 7.6.0, ECOSYSTEM:introduced=0,fixed=7.6.1.
Is there a fix for CVE-2026-97370?: Yes. com.github.junrar:junrar (Maven): upgrade to 7.6.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-97370 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-97370?: Check whether you run Junrar or com.github.junrar:junrar (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

com.github.junrar:junrar (Maven): upgrade to 7.6.1 or later

# set com.github.junrar:junrar to 7.6.1 in your pom.xml or build.gradle

Technical details

The RarVM.ExecuteCode loop is bounded by maxOpCount, but VM_JMP instructions can bypass this limit by calling setIP() with an instruction pointer equal to or greater than codeSize. The setIP() method returns early in this case without updating IP or decrementing maxOpCount, yet the caller ignores the return value and continues the loop, causing the same VM_JMP instruction to execute indefinitely. This is a denial-of-service vulnerability; the RAR VM does not support code execution or reflection, and Java bounds checks prevent memory escape.

Affected products

Junrar Junrar

Identifiers

CVE-2026-97370
GHSA-h9h9-2rmf-rvhp

Timeline

2026-10-15: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.