VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

python-bugzilla: vulnerability history, versions and safety

python-bugzilla is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 3 releases, from Feb 2014 to May 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 H1 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 python-bugzilla vulnerabilities

Vulert verdict on python-bugzilla 3.3.0 i

Updated on 22 Oct 2026

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

Package health score 66/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release 3.3.0 — unaffected i
  • Vulnerabilities on record 2 over 8 years · 0 in the last year i
  • Latest disclosure 14 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 14 packages i
  • Stars 129 i
  • OpenSSF scorecard 3/10 i
  • Last release 24 months ago i
  • Licence GPL-2.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 python-bugzilla, 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
3.3.0 23 Sep 2024 none GPL-2.0 — Details →
3.2.0 12 Jan 2022 none GPL-2.0 — Details →
3.1.0 27 Jul 2021 none GPL-2.0 — Details →
3.0.2 13 Nov 2020 none GPL-2.0 — Details →
3.0.1 07 Oct 2020 none GPL-2.0 — Details →
3.0.0 03 Oct 2020 none GPL-2.0 — Details →
2.5.0 04 Jul 2020 none GPL-2.0 — Details →
2.4.0 29 Jun 2020 none GPL-2.0 — Details →
2.3.0 26 Aug 2019 none GPL-2.0 — Details →
2.2.0 11 Aug 2018 none GPL-2.0 — Details →
2.1.0 30 Mar 2017 none GPL-2.0 — Details →
2.0.0 08 Feb 2017 none GPL-2.0 — Details →
1.2.2 23 Sep 2015 none GPL-2.0 — Details →
1.2.1 22 May 2015 none GPL-2.0 — Details →
1.2.0 13 Apr 2015 none GPL-2.0 — Details →
1.1.0 10 Jun 2014 none GPL-2.0 — Details →
1.0.0 26 Mar 2014 none GPL-2.0 — Details →
0.9.0 20 Jan 2014 none GPL-2.0 — Details →
0.8.0 19 Feb 2013 H1 U1 GPL-2.0 Yes Details →
0.7.0 27 Aug 2012 H1 U1 — Yes Details →
0.6.2 28 Jan 2012 H1 U1 GPL-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 1
  • 2022 1

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 python-bugzilla

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Improper Validation of X.509 Certificates in python-bugzilla 7.5 high 0.9.0 14 May 2022
CVE-2013-2191: python-bugzilla X.509 Certificate Validation Bypass N/A unrated 0.9.0 08 Feb 2014

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 python-bugzilla

Is python-bugzilla safe to use?

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

Vulert scores python-bugzilla 66/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).

Is the latest version of python-bugzilla affected?

No. 3.3.0, 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 python-bugzilla should I use?

3.3.0 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 python-bugzilla have?

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

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

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