VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

zstd: vulnerability history, versions and safety

zstd is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 49 releases, first recorded in Mar 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all zstd vulnerabilities

Vulert verdict on zstd 1.5.7.3 i

Updated on 23 Oct 2026

Careful: 1.5.7.3 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.5.7.3 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 31 Mar 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Depended on by 201 packages i
  • Stars 188 i
  • OpenSSF scorecard 3/10 i
  • Last release 9 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, 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 zstd, 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
1.5.7.3 08 Jan 2026 U1 non-standard No Details →
1.5.7.2 23 Jun 2025 U1 non-standard No Details →
1.5.7.1 07 Jun 2025 U1 non-standard No Details →
1.5.7.0 05 May 2025 U1 non-standard No Details →
1.5.6.8 01 May 2025 U1 non-standard No Details →
1.5.6.7 02 Apr 2025 U1 non-standard No Details →
1.5.6.6 04 Mar 2025 U1 non-standard No Details →
1.5.6.5 01 Mar 2025 U1 non-standard No Details →
1.5.6.4 22 Feb 2025 U1 non-standard No Details →
1.5.6.3 15 Feb 2025 U1 non-standard No Details →
1.5.6.2 20 Jan 2025 U1 non-standard No Details →
1.5.6.1 31 Dec 2024 U1 non-standard No Details →
1.5.5.1 06 Apr 2023 U1 non-standard No Details →
1.5.4.1 23 Mar 2023 U1 non-standard No Details →
1.5.4.0 11 Feb 2023 U1 non-standard No Details →
1.5.2.6 07 Sep 2022 H1 U1 non-standard No Details →
1.5.2.5 02 May 2022 H1 U1 non-standard No Details →
1.5.2.4 20 Apr 2022 H1 U1 non-standard No Details →
1.5.2.3 19 Apr 2022 H1 U1 non-standard No Details →
1.5.2.2 17 Apr 2022 H1 U1 non-standard No Details →
1.5.2.1 17 Apr 2022 H1 U1 non-standard No Details →
1.5.2.0 16 Apr 2022 H1 U1 non-standard No Details →
1.5.1.0 03 Jan 2022 H1 U1 non-standard No Details →
1.5.0.4 03 Dec 2021 H1 U1 non-standard No Details →
1.5.0.3 02 Dec 2021 H1 U1 non-standard No Details →
1.5.0.2 19 May 2021 H1 U1 non-standard No Details →
1.5.0.1 19 May 2021 H1 U1 non-standard No Details →
1.5.0.0 15 May 2021 H1 U1 non-standard No Details →
1.4.9.1 16 Apr 2021 H1 U1 non-standard No Details →
1.4.9.0 16 Apr 2021 H1 U1 non-standard No Details →
1.4.8.1 23 Dec 2020 H1 U1 non-standard No Details →
1.4.8.0 23 Dec 2020 H1 U1 non-standard No Details →
1.4.5.1 28 May 2020 H1 U1 non-standard No Details →
1.4.5.0 26 May 2020 H1 U1 non-standard No Details →
1.4.4.0 05 Nov 2019 H1 U1 non-standard No Details →
1.4.3.2 28 Aug 2019 H1 U1 non-standard No Details →
1.4.1.0 20 Jul 2019 H1 U1 non-standard No Details →
1.4.0.0 28 Apr 2019 H1 U1 non-standard No Details →
1.3.8.1 31 Dec 2018 H1 U1 non-standard No Details →
1.3.8.0 30 Dec 2018 H1 U1 non-standard No Details →
1.3.5.1 02 Oct 2018 H1 U1 non-standard No Details →
1.3.5.0 02 Oct 2018 H1 U1 non-standard No Details →
1.3.4.5 01 Oct 2018 H1 U1 non-standard No Details →
1.3.4.4 09 May 2018 H1 U1 non-standard No Details →
1.3.4.3 06 May 2018 H1 U1 non-standard No Details →
1.3.4 03 Apr 2018 H1 U1 non-standard No Details →
1.3.3 15 Mar 2018 H1 U1 non-standard No Details →
1.3.1 02 Sep 2017 H1 U1 non-standard No Details →
1.3.0.2 11 Aug 2017 H1 U1 non-standard No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2

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

03 Vulnerabilities

Recorded vulnerabilities for zstd

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-4899: zstd Buffer Overrun Vulnerability 7.5 high 1.5.4.0 31 Mar 2023
CVE-2022-4899: Buffer Overrun Vulnerability in zstd N/A unrated No fix published 31 Mar 2023

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 zstd

Is zstd safe to use?

Vulert records 2 vulnerabilities for zstd in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is zstd's Vulert package health score?

Vulert scores zstd 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of zstd affected?

Yes. 1.5.7.3, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of zstd should I use?

1.5.7.3 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 zstd have?

2 vulnerabilities are recorded for zstd in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 zstd vulnerabilities disclosed?

0 vulnerabilities were recorded for zstd in the last 12 months, and the oldest entry in this database dates to 31 Mar 2023. 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 zstd 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 zstd for upcoming vulnerabilities?

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