Skip to content
Fencer Intel
high 8.8

CVE-2019-5063 in the critical feed json

Out-of-bounds Write in OpenCV

published 6y ago modified last mo. also GHSA-m6vm-8g8v-xfjh , PYSEC-2026-2801 , PYSEC-2026-2826 , PYSEC-2026-2840 , PYSEC-2026-724 , EUVD-2021-2226

cvss
8.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
21.1%
EPSS 21.1% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

An exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV 4.1.0. A specially crafted XML file can cause a buffer overflow, resulting in multiple heap corruptions and potential code execution. An attacker can provide a specially crafted file to trigger this vulnerability.

Patch / fix

  • oracle big_data_spatial_and_graph 2.0
  • opencv Debian 14, Debian 13, Debian 12 4.2.0+dfsg-3

debian advisories DEBIAN-CVE-2019-5063

Is CVE-2019-5063 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-5063 updated cvss 8.8

opencv: Heap buffer overflow in persistence_xml.cpp while parsing crafted XML file

  • Red Hat Enterprise Linux 6 opencv, opencv-python Red Hat Enterprise Linux 7 opencv, opencv-core, opencv-python Red Hat Enterprise Linux 8 opencv, opencv-core, opencv-contrib, python3-opencv
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

21.11% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • talosintelligence.com https://talosintelligence.com/vulnerability_reports/TALOS-2019-0852 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
OSV 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
GitHub 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi opencv-python
<=4.1.0.25
 no fix listed
pypi opencv-python-headless
<=4.1.0.25
 no fix listed
pypi opencv-contrib-python
<=4.1.0.25
 no fix listed
pypi opencv-contrib-python-headless
<=4.1.0.25
 no fix listed

Affected products

  • n/a OpenCV

Classification

Weakness
  • CWE-120 Buffer Copy without Checking Size of Input
  • CWE-787 Out-of-bounds Write

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.