PYSEC-2026-725

Vulnerability from pysec - Published: 2026-07-02 14:13 - Updated: 2026-07-06 07:37
VLAI
Details

An exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV, version 4.1.0 (corresponds with OpenCV-Python version 4.1.2.30). 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.

Impacted products
Name purl
opencv-contrib-python-headless pkg:pypi/opencv-contrib-python-headless

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "opencv-contrib-python-headless",
        "purl": "pkg:pypi/opencv-contrib-python-headless"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.2.0.32"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.4.0.14",
        "3.4.1.15",
        "3.4.10.37",
        "3.4.11.39",
        "3.4.11.41",
        "3.4.11.43",
        "3.4.11.45",
        "3.4.13.47",
        "3.4.14.51",
        "3.4.14.53",
        "3.4.15.55",
        "3.4.16.57",
        "3.4.16.59",
        "3.4.17.61",
        "3.4.17.63",
        "3.4.18.65",
        "3.4.2.17",
        "3.4.3.18",
        "3.4.4.19",
        "3.4.5.20",
        "3.4.6.27",
        "3.4.7.28",
        "3.4.8.29",
        "3.4.9.33",
        "4.0.0.21",
        "4.0.1.23",
        "4.0.1.24",
        "4.1.0.25",
        "4.1.1.26",
        "4.1.2.30"
      ]
    }
  ],
  "aliases": [
    "CVE-2019-5064",
    "GHSA-q799-q27x-vp7w"
  ],
  "details": "An exploitable heap buffer overflow vulnerability exists in the data structure persistence functionality of OpenCV, version 4.1.0 (corresponds with OpenCV-Python version 4.1.2.30). 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.",
  "id": "PYSEC-2026-725",
  "modified": "2026-07-06T07:37:01.385478Z",
  "published": "2026-07-02T14:13:13.495435Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2019-5064"
    },
    {
      "type": "WEB",
      "url": "https://github.com/opencv/opencv/issues/15857"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/opencv/opencv-python"
    },
    {
      "type": "WEB",
      "url": "https://github.com/opencv/opencv-python/releases/tag/32"
    },
    {
      "type": "WEB",
      "url": "https://github.com/opencv/opencv/releases/tag/4.2.0"
    },
    {
      "type": "WEB",
      "url": "https://talosintelligence.com/vulnerability_reports/TALOS-2019-0853"
    },
    {
      "type": "WEB",
      "url": "https://www.oracle.com//security-alerts/cpujul2021.html"
    },
    {
      "type": "WEB",
      "url": "https://www.oracle.com/security-alerts/cpuApr2021.html"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/opencv-contrib-python-headless"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-q799-q27x-vp7w"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Out-of-bounds Write in OpenCV"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…