Skip to main content
Public proof of conceptFix available

CVE-2018-12418

A public proof of concept exists; no exploitation attested.

  • Published2018-06-14
  • Fixed in1.0.1
  • WeaknessCWE-835

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2018-06-1416:29CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Versions per branch

NVD · OSV
Junrar project junrar
BranchAffectedFixed in
1.0< 1.0.11.0.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • com.github.junrar:junrarEcho:Mavenall versions · fixed in 1.0.1

Full record on NVD

Fix

  1. Update Junrar project junrar to 1.0.1

Advisories and patches

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Published
2018-06-14
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-5xqr-grq4-qwgx

Frequently asked questions

What is CVE-2018-12418?

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.

Is CVE-2018-12418 actively exploited?

Active exploitation of CVE-2018-12418 has not been confirmed. Its EPSS score was 1.2% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2018-12418?

CVE-2018-12418 has a CVSS v3 base score of 5.5 (MEDIUM severity), with vector string CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.

Running junrar? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record