CVE-2019-5063: PYSEC-2026-724 - Out-of-bounds Write in OpenCV

Quick answers

Is CVE-2019-5063 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2019-5063 being exploited in the wild.

How severe is CVE-2019-5063?

Low severity, with a CVSS score of 3.1, published 2 July 2026.

Which products and versions are affected?

opencv-contrib-python (PyPI) ECOSYSTEM:introduced=0,last_affected=4.1.0.25; opencv-contrib-python-headless (PyPI) ECOSYSTEM:introduced=0,last_affected=4.1.0.25; opencv-python (PyPI) ECOSYSTEM:introduced=0,last_affected=4.1.0.25; opencv-python-headless (PyPI) ECOSYSTEM:introduced=0,last_affected=4.1.0.25.

Is there a fix for CVE-2019-5063?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Am I affected by CVE-2019-5063?

Check whether you run opencv-contrib-python (PyPI), opencv-contrib-python-headless (PyPI), opencv-python (PyPI) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

• opencv-contrib-python (PyPI) ECOSYSTEM:introduced=0,last_affected=4.1.0.25
• opencv-contrib-python-headless (PyPI) ECOSYSTEM:introduced=0,last_affected=4.1.0.25
• opencv-python (PyPI) ECOSYSTEM:introduced=0,last_affected=4.1.0.25
• opencv-python-headless (PyPI) ECOSYSTEM:introduced=0,last_affected=4.1.0.25

Identifiers

• CVE-2019-5063
• GHSA-m6vm-8g8v-xfjh
• PYSEC-2026-2801
• PYSEC-2026-2826
• PYSEC-2026-2840
• PYSEC-2026-724