VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

zip: vulnerability history, versions and safety

zip is a package in the crates.io ecosystem. Vulert records 5 vulnerabilities for it across 111 releases, from Mar 2025 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
5 vulnerabilities recorded H1 U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 10 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all zip vulnerabilities

Vulert verdict on zip 9.0.5 i

Updated on 23 Oct 2026

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

Package health score 71/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 9.0.5 — unaffected i
  • Vulnerabilities on record 5 over 1 year · 3 in the last year i
  • Latest disclosure 10 Oct 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 4 packages i
  • Stars 373 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by crates.io, 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 zip, 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
9.0.5 17 Oct 2026 none MIT — Details →
9.0.4 16 Oct 2026 none MIT — Details →
9.0.3 13 Oct 2026 none MIT — Details →
9.0.2 11 Oct 2026 none MIT — Details →
9.0.1 10 Oct 2026 none MIT — Details →
9.0.0 09 Oct 2026 none MIT — Details →
9.0.0-pre3 11 Aug 2026 none MIT — Details →
9.0.0-pre2 11 May 2026 none MIT — Details →
9.0.0-pre1 06 May 2026 none MIT — Details →
8.6.0 25 Apr 2026 U3 MIT Yes Details →
8.5.1 07 Apr 2026 U3 MIT Yes Details →
8.5.0 01 Apr 2026 U3 MIT Yes Details →
8.4.0 23 Mar 2026 U3 MIT Yes Details →
8.3.1 21 Mar 2026 U3 MIT Yes Details →
8.3.0 19 Mar 2026 U3 MIT Yes Details →
8.2.0 03 Mar 2026 U3 MIT Yes Details →
8.1.0 16 Feb 2026 U3 MIT Yes Details →
8.0.0 15 Feb 2026 U3 MIT Yes Details →
7.4.0 06 Feb 2026 U3 MIT Yes Details →
7.3.0 04 Feb 2026 U3 MIT Yes Details →
7.3.0-pre1 27 Jan 2026 U3 MIT Yes Details →
7.2.0 20 Jan 2026 U3 MIT Yes Details →
7.1.0 14 Jan 2026 U3 MIT Yes Details →
7.0.0 19 Dec 2025 U3 MIT Yes Details →
6.0.0 09 Oct 2025 U3 MIT Yes Details →
5.1.1 11 Sep 2025 U3 MIT Yes Details →
5.1.0 10 Sep 2025 U3 MIT Yes Details →
5.0.1 10 Sep 2025 U3 MIT Yes Details →
5.0.0 05 Sep 2025 U3 MIT Yes Details →
4.6.1 03 Sep 2025 U3 MIT Yes Details →
4.6.0 31 Aug 2025 U3 MIT Yes Details →
4.5.0 21 Aug 2025 U3 MIT Yes Details →
4.4.0 21 Aug 2025 U3 MIT Yes Details →
4.3.0 09 Jul 2025 U3 MIT Yes Details →
4.2.0 23 Jun 2025 U3 MIT Yes Details →
4.1.0 15 Jun 2025 U3 MIT Yes Details →
4.0.0 21 May 2025 U3 MIT Yes Details →
3.0.0 15 May 2025 U3 MIT Yes Details →
2.6.1 04 Apr 2025 U3 MIT Yes Details →
2.6.0 03 Apr 2025 U3 MIT Yes Details →
2.5.0 23 Mar 2025 U3 MIT Yes Details →
2.4.2 19 Mar 2025 U3 MIT Yes Details →
2.4.1 17 Mar 2025 U3 MIT Yes Details →
2.4.0 17 Mar 2025 U3 MIT Yes Details →
2.3.0 16 Mar 2025 U3 MIT Yes Details →
2.2.3 26 Feb 2025 H1 U4 MIT Yes Details →
2.2.2 16 Dec 2024 H1 U4 MIT Yes Details →
2.2.1 21 Nov 2024 H1 U4 MIT Yes Details →
2.2.0 20 Aug 2024 H1 U4 MIT Yes Details →
2.1.6 31 Jul 2024 H1 U4 MIT Yes Details →
2.1.5 20 Jul 2024 H1 U4 MIT Yes Details →
2.1.4 19 Jul 2024 H1 U4 MIT Yes Details →
2.1.3 05 Jun 2024 H1 U4 MIT Yes Details →
2.1.2 02 Jun 2024 H1 U4 MIT Yes Details →
2.1.1 28 May 2024 H1 U4 MIT Yes Details →
2.1.0 25 May 2024 H1 U4 MIT Yes Details →
2.0.0 24 May 2024 H1 U4 MIT Yes Details →
1.3.1 22 May 2024 H1 U4 MIT Yes Details →
1.3.0 17 May 2024 H1 U4 MIT Yes Details →
1.2.3 11 May 2024 U3 MIT Yes Details →
1.2.2 09 May 2024 U3 MIT Yes Details →
1.2.1 07 May 2024 U3 MIT Yes Details →
1.2.0 06 May 2024 U3 MIT Yes Details →
1.1.4 04 May 2024 U3 MIT Yes Details →
1.1.3 30 Apr 2024 U3 MIT Yes Details →
1.1.2 28 Apr 2024 U3 MIT Yes Details →
1.1.1 21 Apr 2024 U3 MIT Yes Details →
1.1.0 20 Apr 2024 U3 MIT Yes Details →
0.6.6 16 May 2023 U3 MIT Yes Details →
0.10.0-alpha.1 07 May 2023 U3 non-standard Yes Details →
0.6.5 06 May 2023 U3 MIT Yes Details →
0.6.4 01 Feb 2023 U3 MIT Yes Details →
0.6.3 13 Oct 2022 U3 MIT Yes Details →
0.6.2 03 Apr 2022 U3 MIT Yes Details →
0.6.1 01 Apr 2022 U3 MIT Yes Details →
0.6.0 20 Mar 2022 U3 MIT Yes Details →
0.5.13 04 Jun 2021 U3 MIT Yes Details →
0.5.12 16 Apr 2021 U3 MIT Yes Details →
0.5.11 01 Mar 2021 U3 MIT Yes Details →
0.5.10 14 Feb 2021 U3 MIT Yes Details →
0.5.9 06 Dec 2020 U3 MIT Yes Details →
0.5.8 10 Sep 2020 U3 MIT Yes Details →
0.5.7 07 Sep 2020 U3 MIT Yes Details →
0.5.6 13 Jun 2020 U3 MIT Yes Details →
0.5.5 01 Mar 2020 U3 MIT Yes Details →
0.5.4 06 Jan 2020 U3 MIT Yes Details →
0.5.3 14 Aug 2019 U3 MIT Yes Details →
0.5.2 06 Apr 2019 U3 MIT Yes Details →
0.5.1 10 Mar 2019 U3 MIT Yes Details →
0.5.0 17 Nov 2018 U3 MIT Yes Details →
0.4.2 22 Jun 2018 U3 MIT Yes Details →
0.4.1 20 Jun 2018 U3 MIT Yes Details →
0.4.0 27 May 2018 U3 MIT Yes Details →
0.3.3 23 May 2018 U3 MIT Yes Details →
0.3.2 20 Apr 2018 U3 MIT Yes Details →
0.3.1 17 Feb 2018 U3 MIT Yes Details →
0.3.0 15 Jan 2018 U3 MIT Yes Details →
0.2.9 09 Jan 2018 U3 MIT Yes Details →
0.2.8 09 Jan 2018 U3 MIT Yes Details →
0.2.7 06 Jan 2018 U3 MIT Yes Details →
0.2.6 17 Aug 2017 U3 — Yes Details →
0.2.5 05 Jul 2017 U3 — Yes Details →
0.2.3 30 Mar 2017 U3 — Yes Details →
0.2.2 06 Mar 2017 U3 — Yes Details →
0.2.1 12 Feb 2017 U3 — Yes Details →
0.2.0 30 Oct 2016 U3 — Yes Details →
0.1.19 07 Oct 2016 U3 — Yes Details →
0.1.18 08 Aug 2016 U3 — Yes Details →
0.1.17 23 Apr 2016 U3 — Yes Details →
0.1.16 22 Feb 2016 U3 — Yes Details →
0.1.15 06 Dec 2015 U3 — Yes Details →
0.1.14 05 Oct 2015 U3 — Yes Details →
0.1.13 05 Oct 2015 U3 — Yes Details →
0.1.12 03 Sep 2015 U3 — Yes Details →
0.1.11 20 Jul 2015 U3 — Yes Details →
0.1.10 13 Jul 2015 U3 — Yes Details →
0.1.9 02 Jul 2015 U3 — Yes Details →
0.1.8 30 Jun 2015 U3 — Yes Details →
0.1.7 25 May 2015 U3 — Yes Details →
0.1.6 20 Apr 2015 U3 — Yes Details →

The newest 120 of 137 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for zip

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Symlink Vulnerability in Zip Package: ZipStreamReader and ZipArchive Permissions Issue 9.1 critical 9.0.0 10 Oct 2026
CVE-2025-29787: zip Package Arbitrary File Write Vulnerability 7.3 high 2.3.0 17 Mar 2025
CVE-2025-29787: zip Package Arbitrary File Write Vulnerability 7.3 high 2.3.0 16 Mar 2025
Privilege Escalation Risk in zip Package: Insecure Preservation of SUID/SGID Bits 7.3 high 9.0.0 09 Oct 2026
Symbolic Link Vulnerability in Zip Package: Risk of External Path Manipulation N/A unrated 9.0.0 09 Oct 2026

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 zip

Is zip safe to use?

Vulert records 5 vulnerabilities for zip in crates.io: 0 critical, 1 high, 0 medium and 0 low, plus 4 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is zip's Vulert package health score?

Vulert scores zip 71/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 zip affected?

No. 9.0.5, 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.

How many vulnerabilities does zip have?

5 vulnerabilities are recorded for zip in the crates.io ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 4 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new zip vulnerabilities disclosed?

3 vulnerabilities were recorded for zip in the last 12 months, and the oldest entry in this database dates to 16 Mar 2025. 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 zip 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 zip for upcoming vulnerabilities?

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