VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

rubyzip: vulnerability history, versions and safety

rubyzip is a package in the RubyGems ecosystem. Vulert records 5 vulnerabilities for it across 49 releases, from Oct 2017 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C2 H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 03 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rubyzip vulnerabilities

Vulert verdict on rubyzip 3.7.0 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 3.7.0 — unaffected i
  • Vulnerabilities on record 5 over 8 years · 1 in the last year i
  • Latest disclosure 03 Sep 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 1,432 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence BSD-2-Clause i

Version list, release dates, licence and dependants published by RubyGems, refreshed 23 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 rubyzip, 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
3.7.0 18 Sep 2026 none BSD-2-Clause — Details →
3.6.0 01 Sep 2026 none BSD-2-Clause — Details →
3.5.0 18 Aug 2026 none BSD-2-Clause — Details →
3.4.1 27 Jun 2026 none BSD-2-Clause — Details →
3.4.0 14 Jun 2026 none BSD-2-Clause — Details →
3.3.1 30 May 2026 H1 BSD-2-Clause Yes Details →
3.3.0 02 May 2026 H1 BSD-2-Clause Yes Details →
3.2.2 02 Nov 2025 H1 BSD-2-Clause Yes Details →
3.2.1 24 Oct 2025 H1 BSD-2-Clause Yes Details →
3.2.0 14 Oct 2025 H1 BSD-2-Clause Yes Details →
3.1.1 26 Sep 2025 H1 BSD-2-Clause Yes Details →
3.1.0 06 Sep 2025 H1 BSD-2-Clause Yes Details →
3.0.2 21 Aug 2025 H1 BSD-2-Clause Yes Details →
3.0.1 08 Aug 2025 H1 BSD-2-Clause Yes Details →
3.0.0 28 Jul 2025 H1 BSD-2-Clause Yes Details →
3.0.0.rc2 08 Feb 2025 H1 BSD-2-Clause Yes Details →
3.0.0.rc1 26 Jan 2025 H1 BSD-2-Clause Yes Details →
2.4.1 05 Jan 2025 H1 BSD-2-Clause Yes Details →
2.4.rc1 08 Apr 2024 H1 BSD-2-Clause Yes Details →
3.0.0.alpha 16 Apr 2023 H1 BSD-2-Clause Yes Details →
2.3.2 05 Jul 2021 H1 BSD-2-Clause Yes Details →
2.3.1 03 Jul 2021 H1 BSD-2-Clause Yes Details →
2.3.0 14 Mar 2020 H1 BSD-2-Clause Yes Details →
2.2.0 01 Feb 2020 H1 BSD-2-Clause Yes Details →
2.1.0 25 Jan 2020 H1 BSD-2-Clause Yes Details →
2.0.0 25 Sep 2019 H1 BSD-2-Clause Yes Details →
1.3.0 25 Sep 2019 H1 BSD-2-Clause Yes Details →
1.2.4 06 Sep 2019 H1 M1 BSD-2-Clause Yes Details →
1.2.3 23 May 2019 H1 M1 BSD-2-Clause Yes Details →
1.2.2 31 Aug 2018 H1 M1 BSD-2-Clause Yes Details →
1.2.1 08 Feb 2017 C1 H1 M1 BSD-2-Clause Yes Details →
1.2.0 19 Feb 2016 C2 H2 M1 BSD-2-Clause Yes Details →
1.1.7 02 Feb 2015 C2 H2 M1 BSD-2-Clause Yes Details →
1.1.6 02 Jul 2014 C2 H2 M1 BSD-2-Clause Yes Details →
1.1.5 02 Jul 2014 C2 H2 M1 BSD-2-Clause Yes Details →
1.1.4 30 May 2014 C2 H2 M1 BSD-2-Clause Yes Details →
1.1.3 06 Apr 2014 C2 H2 M1 — Yes Details →
1.1.2 18 Mar 2014 C2 H2 M1 — Yes Details →
1.1.1 16 Mar 2014 C2 H2 M1 — Yes Details →
1.1.0 01 Nov 2013 C2 H2 M1 — Yes Details →
1.0.0 29 Aug 2013 C2 H2 M1 — Yes Details →
1.0.0.beta1 21 Aug 2013 C2 H2 M1 — Yes Details →
0.9.9 17 Jun 2012 C2 H2 M1 — Yes Details →
0.9.8 26 Apr 2012 C2 H2 M1 — Yes Details →
0.9.7 07 Apr 2012 C2 H2 M1 — Yes Details →
0.9.6.1 08 Feb 2012 C2 H2 M1 — Yes Details →
0.9.5 26 Nov 2011 C2 H2 M1 — Yes Details →
0.9.4 30 Jan 2010 C2 H2 M1 — Yes Details →
0.5.11 25 Jul 2009 C2 H2 M1 — Yes Details →
0.5.12 25 Jul 2009 C2 H2 M1 — Yes Details →
0.5.7 25 Jul 2009 C2 H2 M1 — Yes Details →
0.5.8 25 Jul 2009 C2 H2 M1 — Yes Details →
0.5.9 25 Jul 2009 C2 H2 M1 — Yes Details →
0.9.1 25 Jul 2009 C2 H2 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 2
  • 2019 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for rubyzip

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-5946: Directory Traversal Vulnerability in RubyZip 9.8 critical 1.2.1 24 Oct 2017
CVE-2018-1000544: Directory Traversal vulnerability in rubyzip gem 9.8 critical 1.2.2 06 Sep 2018
CVE-2026-85396: rubyzip Path Traversal Vulnerability 7.5 high 3.4.0 03 Sep 2026
CVE-2019-16892: Denial of Service in Rubyzip 5.5 medium 1.3.0 30 Sep 2019
Directory Traversal Vulnerability in rubyzip N/A high 1.2.1 31 Jul 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: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 rubyzip

Is rubyzip safe to use?

Vulert records 5 vulnerabilities for rubyzip in RubyGems: 2 critical, 2 high, 1 medium and 0 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 rubyzip's Vulert package health score?

Vulert scores rubyzip 73/100, which reads as in good shape. 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 rubyzip affected?

No. 3.7.0, 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 rubyzip should I use?

3.7.0 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 rubyzip have?

5 vulnerabilities are recorded for rubyzip in the RubyGems ecosystem: 2 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rubyzip vulnerabilities disclosed?

1 vulnerability was recorded for rubyzip in the last 12 months, and the oldest entry in this database dates to 24 Oct 2017. 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 rubyzip 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 rubyzip for upcoming vulnerabilities?

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