VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

b2: vulnerability history, versions and safety

b2 is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 44 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 b2 vulnerabilities

Vulert verdict on b2 5.0.2 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 5.0.2 — unaffected 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
  • Stars 638 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i
  • Similar names h2 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 b2, 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
5.0.2 23 Oct 2026 none MIT — Details →
5.0.1 21 Oct 2026 none MIT — Details →
5.0.0 15 Sep 2026 none MIT — Details →
4.8.0 15 Sep 2026 none MIT — Details →
4.7.1 08 Jun 2026 none MIT — Details →
4.7.0 05 May 2026 none MIT — Details →
4.6.0 24 Feb 2026 none MIT — Details →
4.5.1 26 Jan 2026 none MIT — Details →
4.5.0 08 Jan 2026 none MIT — Details →
4.4.2 09 Sep 2025 none MIT — Details →
4.4.1 30 Jul 2025 none MIT — Details →
4.4.0 29 Jul 2025 none MIT — Details →
4.3.3 04 Jun 2025 none MIT — Details →
4.3.2 24 Apr 2025 none MIT — Details →
4.3.1 22 Feb 2025 none MIT — Details →
4.3.0 07 Jan 2025 none MIT — Details →
4.2.0 29 Oct 2024 none MIT — Details →
4.1.0 30 Jul 2024 none MIT — Details →
4.0.3 19 Jun 2024 none MIT — Details →
4.0.2 17 Jun 2024 none MIT — Details →
4.0.1 15 May 2024 none MIT — Details →
4.0.0 13 May 2024 none MIT — Details →
3.19.1 23 Apr 2024 none MIT — Details →
3.19.0 15 Apr 2024 none MIT — Details →
3.18.0 02 Apr 2024 none MIT — Details →
3.17.0 15 Mar 2024 none MIT — Details →
3.16.1 26 Feb 2024 none MIT — Details →
3.16.0 19 Feb 2024 none MIT — Details →
3.15.0 07 Dec 2023 none MIT — Details →
3.14.0 06 Dec 2023 none MIT — Details →
3.13.1 21 Nov 2023 none MIT — Details →
3.13.0 16 Nov 2023 none MIT — Details →
3.12.0 29 Oct 2023 none MIT — Details →
3.11.0 04 Oct 2023 none MIT — Details →
3.10.1 27 Sep 2023 none MIT — Details →
3.10.0 11 Sep 2023 none MIT — Details →
0.0.0 10 Sep 2023 M1 MIT Yes Details →
3.9.0 27 Apr 2023 none MIT — Details →
3.8.0 23 Mar 2023 none MIT — Details →
3.7.1 13 Feb 2023 none MIT — Details →
3.7.0 08 Feb 2023 none MIT — Details →
3.7.0a1 08 Feb 2023 none MIT — Details →
3.6.0 20 Sep 2022 none MIT — Details →
3.5.0 29 Jul 2022 none MIT — Details →
3.4.0 04 May 2022 none MIT — Details →
3.3.0 20 Apr 2022 none MIT — Details →
3.2.1 23 Feb 2022 none MIT — Details →
3.2.0 23 Dec 2021 M1 U1 MIT Yes Details →
3.1.0 02 Nov 2021 M1 U1 MIT Yes Details →
3.0.3 27 Sep 2021 M1 U1 MIT Yes Details →
3.0.2 17 Sep 2021 M1 U1 MIT Yes Details →
3.0.1 10 Aug 2021 M1 U1 MIT Yes Details →
3.0.0 06 Aug 2021 M1 U1 MIT Yes Details →
2.5.1 06 Aug 2021 M1 U1 MIT Yes Details →
2.5.0 21 May 2021 M1 U1 MIT Yes Details →
2.4.0 23 Apr 2021 M1 U1 MIT Yes Details →
2.3.0 25 Mar 2021 M1 U1 MIT Yes Details →
2.2.0 15 Mar 2021 M1 U1 MIT Yes Details →
2.1.0 03 Nov 2020 M1 U1 MIT Yes Details →
2.0.2 15 Jul 2020 M1 U1 MIT Yes Details →
2.0.0 25 Jun 2020 M1 U1 MIT Yes Details →
1.4.2 04 Oct 2019 M1 U1 MIT Yes Details →
1.4.0 26 Apr 2019 M1 U1 MIT Yes Details →
1.3.8 06 Dec 2018 M1 U1 MIT Yes Details →
1.3.6 21 Aug 2018 M1 U1 MIT Yes Details →
1.3.4 10 Aug 2018 M1 U1 MIT Yes Details →
1.3.2 28 Jul 2018 M1 U1 MIT Yes Details →
1.3.0 20 Jul 2018 M1 U1 MIT Yes Details →
1.2.0 06 Jul 2018 M1 U1 MIT Yes Details →
1.1.0 01 Dec 2017 M1 U1 MIT Yes Details →
1.0.0 09 Nov 2017 M1 U1 MIT Yes Details →
0.7.4 09 Nov 2017 M1 U1 MIT Yes Details →
0.7.2 23 Mar 2017 M1 U1 MIT Yes Details →
0.7.0 03 Jan 2017 M1 U1 MIT Yes Details →
0.6.8 14 Oct 2016 M1 U1 MIT Yes Details →
0.6.6 31 Aug 2016 M1 U1 MIT Yes Details →
0.6.4 17 Aug 2016 M1 U1 MIT Yes Details →
0.6.2 14 Jul 2016 M1 U1 MIT Yes Details →
0.6.0 14 Jul 2016 M1 U1 MIT Yes Details →
0.5.6 12 May 2016 M1 U1 MIT Yes Details →
0.5.4 28 Apr 2016 M1 U1 MIT Yes Details →
0.5.2 07 Apr 2016 M1 U1 MIT Yes Details →
0.5.0 06 Apr 2016 M1 U1 MIT Yes Details →
0.4.10 02 Apr 2016 M1 U1 MIT Yes Details →
0.4.8 25 Mar 2016 M1 U1 MIT Yes Details →
0.4.6 22 Mar 2016 M1 U1 MIT Yes Details →
0.4.4 03 Mar 2016 M1 U1 MIT Yes Details →
0.4.2 02 Mar 2016 M1 U1 MIT Yes Details →
0.4.0 17 Feb 2016 M1 U1 MIT Yes Details →
0.3.14 17 Feb 2016 M1 U1 MIT Yes Details →

All 90 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 b2

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2022-23653: B2 Command Line Tool TOCTOU Application Key Disclosure 4.7 medium 3.2.1 24 Feb 2022
CVE-2022-23653: Key Disclosure Vulnerability in B2 Command Line Tool N/A unrated c74029f9f75065e8f7e3c3ec8e0a23fb8204feeb 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 b2

Is b2 safe to use?

Vulert records 2 vulnerabilities for b2 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 b2's Vulert package health score?

Vulert scores b2 80/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 b2 affected?

No. 5.0.2, 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 b2 have?

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

0 vulnerabilities were recorded for b2 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 b2 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 b2 for upcoming vulnerabilities?

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