VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

cbpi4: vulnerability history, versions and safety

cbpi4 is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 30 releases, from May 2024 to Jun 2026. 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 C1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cbpi4 vulnerabilities

Vulert verdict on cbpi4 4.7.7 i

Updated on 23 Oct 2026

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

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

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

  • Current release 4.7.7 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Stars 75 i
  • Last release 1 month ago i
  • Licence GPL-3.0 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 cbpi4, 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
4.7.7 13 Sep 2026 none GPL-3.0 — Details →
4.7.4 28 Feb 2026 none GPL-3.0 — Details →
4.7.3 08 Feb 2026 none GPL-3.0 — Details →
4.7.2 06 Feb 2026 none GPL-3.0 — Details →
4.7.1 05 Jan 2026 none GPL-3.0 — Details →
4.7.0 23 Nov 2025 none GPL-3.0 — Details →
4.6.1 16 Apr 2025 none GPL-3.0 — Details →
4.6.0 20 Mar 2025 none GPL-3.0 — Details →
4.5.1 10 Mar 2025 none GPL-3.0 — Details →
4.5.0 16 Feb 2025 none GPL-3.0 — Details →
4.4.7 20 Dec 2024 none GPL-3.0 — Details →
4.4.6 04 Nov 2024 none GPL-3.0 — Details →
4.4.5 02 Oct 2024 none GPL-3.0 — Details →
4.4.3 13 Jul 2024 none GPL-3.0 — Details →
4.4.2 01 Jul 2024 none GPL-3.0 — Details →
4.4.1 16 Jun 2024 none GPL-3.0 — Details →
4.4.1rc1 10 Jun 2024 none GPL-3.0 — Details →
4.4.1rc0 06 Jun 2024 none GPL-3.0 — Details →
4.4.0 15 Apr 2024 C1 U1 GPL-3.0 Yes Details →
4.3.2 23 Feb 2024 C1 U1 GPL-3.0 Yes Details →
4.3.1 01 Jan 2024 C1 U1 GPL-3.0 Yes Details →
4.3.0 31 Dec 2023 C1 U1 GPL-3.0 Yes Details →
4.2.0 19 Nov 2023 C1 U1 GPL-3.0 Yes Details →
4.2.0rc1 15 Nov 2023 C1 U1 GPL-3.0 Yes Details →
4.2.0a6 01 Nov 2023 C1 U1 GPL-3.0 Yes Details →
4.1.11 30 Jul 2023 C1 U1 GPL-3.0 Yes Details →
4.1.10 10 Jun 2023 C1 U1 GPL-3.0 Yes Details →
4.1.10rc2 02 Jun 2023 C1 U1 GPL-3.0 Yes Details →
4.1.7 30 Mar 2023 C1 U1 GPL-3.0 Yes Details →
4.1.7rc1 26 Mar 2023 C1 U1 GPL-3.0 Yes Details →
4.1.6 10 Mar 2023 C1 U1 GPL-3.0 Yes Details →
4.1.2 26 Feb 2023 C1 U1 GPL-3.0 Yes Details →
4.1.0 01 Feb 2023 C1 U1 GPL-3.0 Yes Details →
4.1.0rc8 29 Jan 2023 C1 U1 GPL-3.0 Yes Details →
4.1.0rc5 23 Jan 2023 C1 U1 GPL-3.0 Yes Details →
4.1.0rc2 20 Jan 2023 C1 U1 GPL-3.0 Yes Details →
4.1.0rc1 15 Jan 2023 C1 U1 GPL-3.0 Yes Details →
4.1.0a3 08 Jan 2023 C1 U1 GPL-3.0 Yes Details →
4.1.0a2 08 Jan 2023 C1 U1 GPL-3.0 Yes Details →
4.0.7 10 Dec 2022 C1 U1 GPL-3.0 Yes Details →
4.0.7rc3 02 Dec 2022 C1 U1 GPL-3.0 Yes Details →
4.0.7rc1 27 Nov 2022 C1 U1 GPL-3.0 Yes Details →
4.0.6 12 May 2022 C1 U1 GPL-3.0 Yes Details →
4.0.5 12 May 2022 C1 U1 GPL-3.0 Yes Details →
4.0.5a16 10 May 2022 C1 U1 — Yes Details →
4.0.5a15 10 May 2022 C1 U1 — Yes Details →
4.0.5a14 10 May 2022 C1 U1 — Yes Details →
4.0.5a13 10 May 2022 C1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for cbpi4

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-3955: CraftBeerPi 4 allows arbitrary code execution 9.8 critical 4.4.1.a1 02 May 2024
CVE-2024-3955: CraftBeerPi 4 Arbitrary Code Execution Vulnerability 9.8 critical 4.4.1.a1 29 Jun 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 cbpi4

Is cbpi4 safe to use?

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

Vulert scores cbpi4 73/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 cbpi4 affected?

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

Which version of cbpi4 should I use?

4.7.7 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 cbpi4 have?

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

1 vulnerability was recorded for cbpi4 in the last 12 months, and the oldest entry in this database dates to 02 May 2024. 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 cbpi4 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 cbpi4 for upcoming vulnerabilities?

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