VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

b2sdk: vulnerability history, versions and safety

b2sdk is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 75 releases, first recorded in Feb 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 M1 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 b2sdk vulnerabilities

Vulert verdict on b2sdk 2.13.2 i

Updated on 23 Oct 2026

Action needed: 2.13.2 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 74/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 2.13.2 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 Feb 2022 i
  • Highest CVSS 4.7 i
  • With no published fix 0 i
  • Depended on by 30 packages i
  • Stars 214 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT 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 b2sdk, 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
2.13.2 21 Oct 2026 U1 MIT Yes Details →
2.13.1 04 Oct 2026 U1 MIT Yes Details →
2.13.0 14 Sep 2026 U1 MIT Yes Details →
2.12.0 05 May 2026 U1 MIT Yes Details →
2.11.0 30 Apr 2026 U1 MIT Yes Details →
2.10.4 02 Mar 2026 U1 MIT Yes Details →
2.10.3 22 Feb 2026 U1 MIT Yes Details →
2.10.2 16 Dec 2025 U1 MIT Yes Details →
2.10.1 26 Oct 2025 U1 MIT Yes Details →
2.10.0 17 Aug 2025 U1 MIT Yes Details →
2.9.4 11 Jun 2025 U1 MIT Yes Details →
2.9.3 29 May 2025 U1 MIT Yes Details →
2.9.2 29 May 2025 U1 MIT Yes Details →
2.9.1 28 May 2025 U1 MIT Yes Details →
2.8.1 23 Apr 2025 U1 MIT Yes Details →
2.8.0 23 Jan 2025 U1 MIT Yes Details →
2.7.0 12 Dec 2024 U1 MIT Yes Details →
2.6.0 28 Oct 2024 U1 MIT Yes Details →
2.5.1 15 Aug 2024 U1 MIT Yes Details →
2.5.0 30 Jul 2024 U1 MIT Yes Details →
2.4.1 19 Jun 2024 U1 MIT Yes Details →
2.4.0 17 Jun 2024 U1 MIT Yes Details →
2.3.0 15 May 2024 U1 MIT Yes Details →
2.2.1 09 May 2024 U1 MIT Yes Details →
2.2.0 08 May 2024 U1 MIT Yes Details →
2.1.0 15 Apr 2024 U1 MIT Yes Details →
2.0.0 02 Apr 2024 U1 MIT Yes Details →
1.33.0 15 Mar 2024 U1 MIT Yes Details →
1.32.0 26 Feb 2024 U1 MIT Yes Details →
1.31.0 19 Feb 2024 U1 MIT Yes Details →
1.30.1 02 Feb 2024 U1 MIT Yes Details →
1.29.1 23 Jan 2024 U1 MIT Yes Details →
1.29.0 13 Dec 2023 U1 MIT Yes Details →
1.28.0 06 Dec 2023 U1 MIT Yes Details →
1.27.0 26 Nov 2023 U1 MIT Yes Details →
1.26.0 21 Nov 2023 U1 MIT Yes Details →
1.25.0 15 Nov 2023 U1 MIT Yes Details →
1.24.1 27 Sep 2023 U1 MIT Yes Details →
1.24.0 31 Aug 2023 U1 MIT Yes Details →
1.23.0 10 Aug 2023 U1 MIT Yes Details →
1.22.1 24 Jul 2023 U1 MIT Yes Details →
1.22.0 21 Jul 2023 U1 MIT Yes Details →
1.21.0 17 Apr 2023 U1 MIT Yes Details →
1.20.0 23 Mar 2023 U1 MIT Yes Details →
1.19.0 24 Jan 2023 U1 MIT Yes Details →
1.18.0 20 Sep 2022 U1 MIT Yes Details →
1.17.3 15 Jul 2022 U1 MIT Yes Details →
1.17.2 23 Jun 2022 U1 MIT Yes Details →
1.17.1 22 Jun 2022 U1 MIT Yes Details →
1.17.0 22 Jun 2022 U1 MIT Yes Details →
1.16.0 28 Apr 2022 U1 MIT Yes Details →
1.15.0 12 Apr 2022 U1 MIT Yes Details →
1.14.1 23 Feb 2022 U1 MIT Yes Details →
1.14.0 23 Dec 2021 M1 U1 MIT Yes Details →
1.13.0 24 Oct 2021 M1 U1 MIT Yes Details →
1.12.0 06 Aug 2021 M1 U1 MIT Yes Details →
1.11.0 24 Jun 2021 M1 U1 MIT Yes Details →
1.10.0 23 Jun 2021 M1 U1 MIT Yes Details →
1.9.0 07 Jun 2021 M1 U1 MIT Yes Details →
1.8.0 21 May 2021 M1 U1 MIT Yes Details →
1.7.0 22 Apr 2021 M1 U1 MIT Yes Details →
1.6.0 08 Apr 2021 M1 U1 MIT Yes Details →
1.5.0 25 Mar 2021 M1 U1 MIT Yes Details →
1.4.0 03 Mar 2021 M1 U1 MIT Yes Details →
1.3.0 13 Jan 2021 M1 U1 MIT Yes Details →
1.2.0 03 Nov 2020 M1 U1 MIT Yes Details →
1.1.4 15 Jul 2020 M1 U1 MIT Yes Details →
1.1.2 07 Jul 2020 M1 U1 MIT Yes Details →
1.1.0 24 Jun 2020 M1 U1 MIT Yes Details →
1.0.2 15 Oct 2019 M1 U1 MIT Yes Details →
1.0.0 03 Oct 2019 M1 U1 MIT Yes Details →
1.0.0rc1 10 Jul 2019 M1 U1 MIT Yes Details →
0.1.8 28 Jun 2019 M1 U1 MIT Yes Details →
0.1.6 25 Apr 2019 M1 U1 MIT Yes Details →
0.1.4 04 Apr 2019 M1 U1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 b2sdk

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-23651: b2-sdk-python TOCTOU application key disclosure 4.7 medium 1.14.1 24 Feb 2022
CVE-2022-23651: Key Disclosure Vulnerability in b2-sdk-python N/A unrated 62476638986e5b6d7459aca5ef8ce220760226e0 23 Feb 2022

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 b2sdk

Is b2sdk safe to use?

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

Vulert scores b2sdk 74/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 b2sdk affected?

Yes. 2.13.2, 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 b2sdk have?

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

0 vulnerabilities were recorded for b2sdk in the last 12 months, and the oldest entry in this database dates to 23 Feb 2022. 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 b2sdk 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 b2sdk for upcoming vulnerabilities?

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