CVE-2019-16249 is a medium-severity (CVSS 5.3) Out-of-bounds Read vulnerability in opencv-python. A fix is available for opencv-python — see the affected versions and patch details below.
Out-of-bounds Read in OpenCV
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2019-16249 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
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
OpenCV 4.1.1 has an out-of-bounds read in hal_baseline::v_load in core/hal/intrin_sse.hpp when called from computeSSDMeanNorm in modules/video/src/dis_flow.cpp.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | opencv-python | all versions | 4.1.2.30pip install --upgrade 'opencv-python==4.1.2.30' |
| 🐍PyPI | opencv-python-headless | all versions | 4.1.2.30pip install --upgrade 'opencv-python-headless==4.1.2.30' |
| 🐍PyPI | opencv-contrib-python | all versions | 4.1.2.30pip install --upgrade 'opencv-contrib-python==4.1.2.30' |
| 🐍PyPI | opencv-contrib-python-headless | all versions | 4.1.2.30pip install --upgrade 'opencv-contrib-python-headless==4.1.2.30' |
Affected Products
opencvopencvDetection & 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.1.2.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16249 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.
Frequently Asked Questions
Is CVE-2019-16249 in your dependencies?
Find it across PyPI, including transitive dependencies.