VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

bitsandbytes: vulnerability history, versions and safety

bitsandbytes is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

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

Vulert verdict on bitsandbytes 0.50.2 i

Updated on 23 Oct 2026

Good news: 0.50.2, the version you would install today, has no known vulnerabilities.

Package health score 95/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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

  • Current release 0.50.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 561 packages i
  • Stars 8,529 i
  • Last release 1 month ago 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 bitsandbytes, 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
0.50.2 27 Aug 2026 none MIT — Details →
0.50.1 13 Aug 2026 none MIT — Details →
0.50.0 25 Jul 2026 none MIT — Details →
0.49.2 16 Feb 2026 none MIT — Details →
0.49.1 08 Jan 2026 none MIT — Details →
0.49.0 11 Dec 2025 none MIT — Details →
0.48.2 29 Oct 2025 none MIT — Details →
0.48.1 02 Oct 2025 none MIT — Details →
0.48.0 30 Sep 2025 none MIT — Details →
0.47.0 11 Aug 2025 none non-standard — Details →
0.46.1 02 Jul 2025 none non-standard — Details →
0.46.0 27 May 2025 none non-standard — Details →
0.45.5 07 Apr 2025 none non-standard — Details →
0.45.4 25 Mar 2025 none non-standard — Details →
0.45.3 24 Feb 2025 none non-standard — Details →
0.45.2 06 Feb 2025 none non-standard — Details →
0.45.1 23 Jan 2025 none non-standard — Details →
0.45.0 05 Dec 2024 none MIT — Details →
0.44.1 30 Sep 2024 none MIT — Details →
0.44.0 24 Sep 2024 none MIT — Details →
0.43.3 30 Jul 2024 none MIT — Details →
0.43.2 23 Jul 2024 none MIT — Details →
0.43.1 11 Apr 2024 none MIT — Details →
0.43.0 08 Mar 2024 none MIT — Details →
0.42.0 08 Jan 2024 none MIT — Details →
0.41.3.post2 11 Dec 2023 none MIT — Details →
0.41.3.post1 11 Dec 2023 none MIT — Details →
0.41.3 06 Dec 2023 none MIT — Details →
0.41.2.post2 09 Nov 2023 none MIT — Details →
0.41.2.post1 08 Nov 2023 none MIT — Details →
0.41.2 08 Nov 2023 none MIT — Details →
0.41.1 04 Aug 2023 none MIT — Details →
0.41.0 22 Jul 2023 none MIT — Details →
0.40.2 17 Jul 2023 none MIT — Details →
0.40.1.post1 15 Jul 2023 none MIT — Details →
0.40.1 14 Jul 2023 none MIT — Details →
0.40.0.post4 12 Jul 2023 none MIT — Details →
0.40.0.post3 11 Jul 2023 none MIT — Details →
0.40.0.post2 11 Jul 2023 none MIT — Details →
0.40.0.post1 10 Jul 2023 none MIT — Details →
0.40.0 10 Jul 2023 none MIT — Details →
0.39.1 20 Jun 2023 none MIT — Details →
0.39.0 24 May 2023 none MIT — Details →
0.38.1 12 Apr 2023 none MIT — Details →
0.38.0.post2 12 Apr 2023 none MIT — Details →
0.38.0.post1 11 Apr 2023 none MIT — Details →
0.38.0 11 Apr 2023 none MIT — Details →
0.37.2 21 Mar 2023 none MIT — Details →
0.37.1 12 Mar 2023 none MIT — Details →
0.37.0 02 Feb 2023 none MIT — Details →
0.36.0.post2 04 Jan 2023 none MIT — Details →
0.36.0 04 Jan 2023 none MIT — Details →
0.35.4 01 Nov 2022 none MIT — Details →
0.35.3 27 Oct 2022 none MIT — Details →
0.35.2 27 Oct 2022 none MIT — Details →
0.35.0 10 Oct 2022 none MIT — Details →
0.34.0 20 Sep 2022 none MIT — Details →
0.33.0 11 Sep 2022 none MIT — Details →
0.32.3 08 Sep 2022 none MIT — Details →
0.32.2 23 Aug 2022 none MIT — Details →
0.32.0 17 Aug 2022 none MIT — Details →
0.31.8 09 Aug 2022 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for bitsandbytes

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 bitsandbytes

Is bitsandbytes safe to use?

Vulert has no vulnerabilities on record for bitsandbytes in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is bitsandbytes's Vulert package health score?

Vulert scores bitsandbytes 95/100, which reads as healthy. 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 bitsandbytes affected?

No. 0.50.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.

Which version of bitsandbytes should I use?

0.50.2 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 bitsandbytes have?

0 vulnerabilities are recorded for bitsandbytes in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new bitsandbytes vulnerabilities disclosed?

0 vulnerabilities were recorded for bitsandbytes in the last 12 months. 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 bitsandbytes 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 bitsandbytes for upcoming vulnerabilities?

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