CVE-2019-14493: opencv-python NULL Pointer Dereference Vulnerability
Summary
CVE-2019-14493: NULL Pointer Dereference in OpenCV. Affects opencv-python versions < 4.1.1.26. Fixed in 4.1.1.26. How to fix ↓
Also tracked for
- opencv-contrib-python · PyPI
- opencv-python-headless · PyPI
- opencv-contrib-python-headless · PyPI
- opencv · Debian:11
The same CVE-2019-14493 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
OpenCV is an open-source computer vision and machine learning software library. It provides a common infrastructure for computer vision applications and accelerates the usage of machine perception in commercial products. The opencv-python package allows Python developers to access OpenCV functionalities. However, prior to version 4.1.1.26, it was susceptible to a NULL pointer dereference vulnerability, which could lead to application crashes and potential denial of service.
Vulnerability Detail
An issue was discovered in OpenCV before version 4.1.1 (specifically in opencv-python before 4.1.1.26). The vulnerability arises from a NULL pointer dereference in the function cv::XMLParser::parse located in modules/core/src/persistence.cpp. This flaw can be exploited by attackers to cause the application to crash, leading to a denial of service. The vulnerability has a CVSS score of 7.5, indicating a high severity level.
How To Fix
Latest published version: 5.0.0.93 as of 23 Oct 2026
pip install --upgrade "opencv-python==5.0.0.93"
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
4.1.1.26
This is the first release that contains the fix.
pip install --upgrade "opencv-python==4.1.1.26"
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, you can avoid using the specific functionality that triggers the NULL pointer dereference until you can update the package. However, it is strongly advised to apply the patch as soon as possible to mitigate any risks.
Conclusion
The NULL pointer dereference vulnerability in opencv-python (CVE-2019-14493) poses a significant risk to applications using this library. It is crucial to update to the patched version to mitigate the risk of denial of service. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for opencv-python →
FAQ
A NULL pointer dereference occurs when a program attempts to access memory that has not been allocated, leading to unpredictable behavior or crashes.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
The primary consequence is a denial of service, where the application may crash, affecting its availability and functionality.
Yes, you should upgrade to version 4.1.1.26 or later to ensure that the vulnerability is patched.
Vulert monitors and alerts in real-time for open-source vulnerabilities in your software using just the Pipfile.lock, making it easy to stay informed about potential risks.
Related vulnerabilities
Recent vulnerabilities recorded for opencv-python.