CVE-2018-12418 is a medium-severity (CVSS 5.5) CWE-835 vulnerability in com.github.junrar:junrar. A fix is available for com.github.junrar:junrar — see the affected versions and patch details below.
Junrar vulnerable to Infinite Loop
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.github.junrar:junrarReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Archive.java in Junrar before 1.0.1, as used in Apache Tika and other products, is affected by a denial of service vulnerability due to an infinite loop when handling corrupt RAR files.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.github.junrar:junrar | all versions | 1.0.1com.github.junrar:junrar:1.0.1 |
Affected Products
junrarjunrar_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.github.junrar:junrar, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.github.junrar:junrar to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-12418 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2018-12418 in your dependencies?
Find it across Maven, including transitive dependencies.