CVE-2019-5064 — opencv-python
HIGHCVE-2019-5064 is a high-severity (CVSS 8.8) CWE-120 vulnerability in opencv-python. 1 public exploit reference exists, so weaponization risk is real. A fix is available for opencv-python — see the affected versions and patch details below.
Out-of-bounds Write in OpenCV
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2019-5064 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
opencv-python🐍opencv-python-headless🐍opencv-contrib-python🐍opencv-contrib-python-headlessReal-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
An exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV, before version 4.2.0. A specially crafted JSON file can cause a buffer overflow, resulting in multiple heap corruptions and potentially code execution. An attacker can provide a specially crafted file to trigger this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | opencv-python | all versions | 4.2.0.32pip install --upgrade 'opencv-python==4.2.0.32' |
| 🐍PyPI | opencv-python-headless | all versions | 4.2.0.32pip install --upgrade 'opencv-python-headless==4.2.0.32' |
| 🐍PyPI | opencv-contrib-python | all versions | 4.2.0.32pip install --upgrade 'opencv-contrib-python==4.2.0.32' |
| 🐍PyPI | opencv-contrib-python-headless | all versions | 4.2.0.32pip install --upgrade 'opencv-contrib-python-headless==4.2.0.32' |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for opencv-python, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update opencv-python to 4.2.0.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-5064 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-5064 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2019-5064. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-5064 in your dependencies?
O3 Security finds CVE-2019-5064 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.