VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

bsdiff4: vulnerability history, versions and safety

bsdiff4 is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 21 releases, from Jul 2020 to May 2022. 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
0 with no fix published

Every vulnerability has a patched version to move to.

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 bsdiff4 vulnerabilities

Vulert verdict on bsdiff4 1.3.1 i

Updated on 23 Oct 2026

Action needed: 1.3.1 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 72/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 1.3.1 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 7.8 i
  • With no published fix 0 i
  • Depended on by 25 packages i
  • Stars 145 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, 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 bsdiff4, 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.3.1 21 Oct 2026 U1 non-standard Yes Details →
1.3.0 20 Oct 2026 U1 non-standard Yes Details →
1.2.6 19 Feb 2025 U1 non-standard Yes Details →
1.2.5 10 Oct 2024 U1 non-standard Yes Details →
1.2.4 02 Nov 2023 U1 non-standard Yes Details →
1.2.3 24 Feb 2023 U1 non-standard Yes Details →
1.2.2 09 Mar 2022 U1 non-standard Yes Details →
1.2.1 11 Apr 2021 U1 non-standard Yes Details →
1.2.0 19 Jul 2020 U1 non-standard Yes Details →
1.1.9 20 Nov 2019 H1 U1 non-standard Yes Details →
1.1.8 17 Nov 2019 H1 U1 non-standard Yes Details →
1.1.7 15 Nov 2019 H1 U1 non-standard Yes Details →
1.1.6 13 Nov 2019 H1 U1 non-standard Yes Details →
1.1.5 19 Jun 2018 H1 U1 non-standard Yes Details →
1.1.4 06 Apr 2013 H1 U1 — Yes Details →
1.1.3 20 Jan 2013 H1 U1 — Yes Details →
1.1.2 27 Nov 2012 H1 U1 — Yes Details →
1.1.1 14 Mar 2012 H1 U1 — Yes Details →
1.1.0 11 Feb 2012 H1 U1 — Yes Details →
1.0.1 12 Jun 2011 H1 U1 — Yes Details →
1.0.0 23 May 2011 H1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2022 1

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 bsdiff4

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2020-15904: bsdiff4 out-of-bounds write via patch file 7.8 high 1.2.0 24 May 2022
CVE-2020-15904: Buffer Overflow in bsdiff4 N/A unrated 49a4cee2feef7deaf9d89e5e793a8824930284d7 22 Jul 2020

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 bsdiff4

Is bsdiff4 safe to use?

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

Vulert scores bsdiff4 72/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 bsdiff4 affected?

Yes. 1.3.1, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does bsdiff4 have?

2 vulnerabilities are recorded for bsdiff4 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 bsdiff4 vulnerabilities disclosed?

0 vulnerabilities were recorded for bsdiff4 in the last 12 months, and the oldest entry in this database dates to 22 Jul 2020. 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 bsdiff4 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 bsdiff4 for upcoming vulnerabilities?

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