VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.github.junrar:junrar: vulnerability history, versions and safety

com.github.junrar:junrar is a package in the Maven ecosystem. Vulert records 6 vulnerabilities for it across 28 releases, from Oct 2018 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded H2 M3 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all com.github.junrar:junrar vulnerabilities

Vulert verdict on com.github.junrar:junrar 8.1.2 i

Updated on 22 Oct 2026

Good news: 8.1.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 6.

Package health score 64/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

What to do: Stay on 8.1.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 8.1.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 8.1.2 — unaffected i
  • Vulnerabilities on record 6 over 7 years · 4 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 318 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for com.github.junrar:junrar, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
8.1.2 09 Oct 2026 none non-standard — Details →
8.1.1 31 Aug 2026 none non-standard — Details →
8.1.0 03 Aug 2026 none non-standard — Details →
8.0.0 23 Jul 2026 none non-standard — Details →
7.6.1 21 Jul 2026 none non-standard — Details →
7.6.0 13 May 2026 H1 L1 non-standard Yes Details →
7.5.10 15 Apr 2026 H1 L1 non-standard Yes Details →
7.5.9 13 Apr 2026 H1 L1 non-standard Yes Details →
7.5.8 26 Feb 2026 H1 M1 L1 non-standard Yes Details →
7.5.7 17 Oct 2025 H1 M2 L1 non-standard Yes Details →
7.5.6 16 Oct 2025 H1 M2 L1 non-standard Yes Details →
7.5.5 18 Jul 2023 H1 M2 L1 non-standard Yes Details →
7.5.4 04 Nov 2022 H1 M2 L1 non-standard Yes Details →
7.5.3 08 Aug 2022 H1 M2 L1 non-standard Yes Details →
7.5.2 31 May 2022 H1 M2 L1 non-standard Yes Details →
7.5.1 28 Apr 2022 H1 M2 L1 non-standard Yes Details →
7.5.0 20 Mar 2022 H1 M2 L1 non-standard Yes Details →
7.4.1 27 Jan 2022 H1 M2 L1 non-standard Yes Details →
7.4.0 01 Nov 2020 H2 M2 L1 non-standard Yes Details →
7.3.0 03 Aug 2020 H2 M2 L1 non-standard Yes Details →
7.2.0 28 Jul 2020 H2 M2 L1 non-standard Yes Details →
7.1.0 27 Jul 2020 H2 M2 L1 non-standard Yes Details →
7.0.0 25 Jul 2020 H2 M2 L1 non-standard Yes Details →
6.0.1 21 Jul 2020 H2 M2 L1 non-standard Yes Details →
6.0.0 19 Jul 2020 H2 M2 L1 non-standard Yes Details →
5.0.0 18 Jul 2020 H2 M2 L1 non-standard Yes Details →
4.0.0 12 Mar 2019 H2 M2 L1 non-standard Yes Details →
3.1.0 02 Dec 2018 H2 M2 L1 non-standard Yes Details →
3.0.0 19 Aug 2018 H2 M2 L1 non-standard Yes Details →
2.0.0 18 Jun 2018 H2 M2 L1 non-standard Yes Details →
1.0.1 02 Jun 2018 H2 M2 L1 non-standard Yes Details →
1.0.0 26 Apr 2018 H2 M3 L1 non-standard Yes Details →
0.7 05 Sep 2012 H2 M3 L1 non-standard Yes Details →

All 33 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2022 1
  • 2026 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 6 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for com.github.junrar:junrar

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-23596: Junrar Vulnerable to Infinite Loop via Extracting Crafted RAR Archive 7.5 high 7.4.1 01 Feb 2022
CVE-2026-97370: Junrar Denial of Service Vulnerability Due to Infinite Loop in RAR4 Extraction 7.5 high 7.6.1 15 Oct 2026
CVE-2026-28208: Junrar Arbitrary File Write Vulnerability Due to Backslash Path Traversal Bypass 5.9 medium 7.5.8 27 Feb 2026
Path Traversal Vulnerability in Junrar Package: Arbitrary File Writing Risk 5.9 medium 7.5.10 16 Apr 2026
CVE-2018-12418: Junrar Infinite Loop Denial of Service Vulnerability 5.5 medium 1.0.1 17 Oct 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About com.github.junrar:junrar

Is com.github.junrar:junrar safe to use?

Vulert records 6 vulnerabilities for com.github.junrar:junrar in Maven: 0 critical, 2 high, 3 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is com.github.junrar:junrar's Vulert package health score?

Vulert scores com.github.junrar:junrar 64/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of com.github.junrar:junrar affected?

No. 8.1.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of com.github.junrar:junrar should I use?

8.1.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does com.github.junrar:junrar have?

6 vulnerabilities are recorded for com.github.junrar:junrar in the Maven ecosystem: 0 critical, 2 high, 3 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new com.github.junrar:junrar vulnerabilities disclosed?

4 vulnerabilities were recorded for com.github.junrar:junrar in the last 12 months, and the oldest entry in this database dates to 17 Oct 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of com.github.junrar:junrar are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor com.github.junrar:junrar for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the com.github.junrar:junrar version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.