CVE-2013-2191 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in python-bugzilla. A fix is available for python-bugzilla — see the affected versions and patch details below.
python-bugzilla has improper validation of X.509 certificates
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
python-bugzillaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
python-bugzilla before 0.9.0 does not validate X.509 certificates, which allows man-in-the-middle attackers to spoof Bugzilla servers via a crafted certificate.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | python-bugzilla | all versions | 0.9.0pip install --upgrade 'python-bugzilla==0.9.0' |
Affected Products
fedorafedoraprojectopensuseopensusepython-bugzillapython_bugzilla_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for python-bugzilla, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update python-bugzilla to 0.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2191 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2013-2191 in your dependencies?
Find it across PyPI, including transitive dependencies.