CVE-2013-6418 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in pywbem. A fix is available for pywbem — see the affected versions and patch details below.
PyWBEM TOCTOU vulnerability in certificate validation
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
pywbemReal-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
PyWBEM 0.7 and earlier uses a separate connection to validate X.509 certificates, which allows man-in-the-middle attackers to spoof a peer via an arbitrary certificate.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | pywbem | all versions | 0.8.1pip install --upgrade 'pywbem==0.8.1' |
Affected Products
pywbempywbem_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pywbem, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pywbem to 0.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-6418 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-6418 in your dependencies?
Find it across PyPI, including transitive dependencies.