CVE-2017-18009: PYSEC-2026-702 - Out-of-bounds Read in OpenCV

CVE-2017-18009 · Severity: low · CVSS 3 · Published 2026-07-02

Out-of-bounds Read in OpenCV

Technologies: opencv-contrib-python (PyPI), opencv-python (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2017-18009 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-18009 being exploited in the wild.
How severe is CVE-2017-18009?
Low severity, with a CVSS score of 3, published 2 July 2026.
Which products and versions are affected?
opencv-contrib-python (PyPI) ECOSYSTEM:introduced=0,fixed=3.4.1.15; opencv-python (PyPI) ECOSYSTEM:introduced=0,fixed=3.4.1.15.
Is there a fix for CVE-2017-18009?
Yes. opencv-contrib-python (PyPI): upgrade to 3.4.1.15 or later; opencv-python (PyPI): upgrade to 3.4.1.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-18009?
Check whether you run opencv-contrib-python (PyPI) or opencv-python (PyPI) 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.

How to fix

  • opencv-contrib-python (PyPI): upgrade to 3.4.1.15 or later
    pip install "opencv-contrib-python>=3.4.1.15"
  • opencv-python (PyPI): upgrade to 3.4.1.15 or later
    pip install "opencv-python>=3.4.1.15"

Affected products

  • opencv-contrib-python (PyPI) ECOSYSTEM:introduced=0,fixed=3.4.1.15
  • opencv-python (PyPI) ECOSYSTEM:introduced=0,fixed=3.4.1.15

Identifiers

  • CVE-2017-18009
  • GHSA-83rh-hx5x-q9p5
  • PYSEC-2026-2810
  • PYSEC-2026-702

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.