Vulnerability Database · PyPI · Package report

calibreweb: vulnerability history, versions and safety

calibreweb is a package in the PyPI ecosystem. Vulert records 36 vulnerabilities for it across 16 releases, from Jan 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
36 vulnerabilities recorded C4 H4 M9 L1 U18
i
8 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
16 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on calibreweb 0.6.27 i

Updated on 23 Oct 2026

Careful: 0.6.27 has 10 known vulnerabilities, and 8 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.6.27 — affected i
  • Vulnerabilities on record 36 over 4 years · 16 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 8 i
  • Stars 18,384 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 months ago i
  • Licence GPL-3.0-or-later 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 calibreweb, 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.6.27 08 Aug 2026 H1 M2 L1 U6 GPL-3.0-or-later No Details →
0.6.26 06 Feb 2026 H1 M2 L1 U6 non-standard No Details →
0.6.25 24 Aug 2025 L1 U1 non-standard No Details →
0.6.24 16 Nov 2024 H1 M1 L1 U3 non-standard No Details →
0.6.23 05 Aug 2024 H1 M1 L1 U3 non-standard No Details →
0.6.22 06 Jul 2024 H1 M1 L1 U3 non-standard No Details →
0.6.21 21 Oct 2023 H1 M2 L1 U4 non-standard No Details →
0.6.20 27 Mar 2023 H1 M2 L1 U4 non-standard No Details →
0.6.19 31 Jul 2022 H2 M3 L1 U6 non-standard No Details →
0.6.18 03 Apr 2022 H2 M3 L1 U6 non-standard No Details →
0.6.17 06 Mar 2022 C1 H2 M3 L1 U7 non-standard No Details →
0.6.16 24 Jan 2022 C3 H2 M3 L1 U9 non-standard No Details →
0.6.15 16 Jan 2022 C3 H3 M5 L1 U12 non-standard No Details →
0.6.14 31 Oct 2021 C4 H4 M9 L1 U18 non-standard No Details →
0.6.13 25 Sep 2021 C4 H4 M9 L1 U18 non-standard No Details →
0.6.12 22 May 2021 C4 H4 M9 L1 U18 non-standard No Details →

All 16 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 12
  • 2023 2
  • 2024 4
  • 2025 3
  • 2026 15

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

03 Vulnerabilities

Recorded vulnerabilities for calibreweb

The 5 most severe of 36 vulnerabilities recorded for this package

Search all 36 in the database →

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 calibreweb

Is calibreweb safe to use?

Vulert records 36 vulnerabilities for calibreweb in PyPI: 4 critical, 4 high, 9 medium and 1 low, plus 18 not yet rated. 8 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is calibreweb's Vulert package health score?

Vulert scores calibreweb 50/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of calibreweb affected?

Yes. 0.6.27, the version you would install today, has 10 known vulnerabilities, and 8 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of calibreweb should I use?

0.6.27 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 calibreweb have?

36 vulnerabilities are recorded for calibreweb in the PyPI ecosystem: 4 critical, 4 high, 9 medium and 1 low, plus 18 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 calibreweb vulnerabilities disclosed?

16 vulnerabilities were recorded for calibreweb in the last 12 months, and the oldest entry in this database dates to 21 Jan 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 calibreweb 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 calibreweb for upcoming vulnerabilities?

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