Vulnerability Database · PyPI · Package report

opencv-python: vulnerability history, versions and safety

opencv-python is a package in the PyPI ecosystem. Vulert records 62 vulnerabilities for it across 63 releases, from Oct 2021 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
62 vulnerabilities recorded H23 M8 U31
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
30 in the last 12 months

Most recent disclosure 09 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on opencv-python 5.0.0.93 i

Updated on 22 Oct 2026

Careful: 5.0.0.93 has 4 known vulnerabilities, and 4 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 59/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 5.0.0.93 — affected i
  • Vulnerabilities on record 62 over 4 years · 30 in the last year i
  • Latest disclosure 09 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 4 i
  • Depended on by 8,838 packages i
  • Stars 5,429 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for opencv-python, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.14.0.94 28 Jul 2026 H2 U2 Apache-2.0 No Details →
5.0.0.93 02 Jul 2026 H2 U2 Apache-2.0 No Details →
4.13.0.92 05 Feb 2026 H2 U2 Apache-2.0 No Details →
4.13.0.90 18 Jan 2026 H2 U2 Apache-2.0 No Details →
4.12.0.88 07 Jul 2025 H2 U2 Apache-2.0 No Details →
4.11.0.86 16 Jan 2025 H2 U2 Apache-2.0 No Details →
4.10.0.84 17 Jun 2024 H2 U2 Apache-2.0 No Details →
4.10.0.82 03 Jun 2024 H2 U2 Apache-2.0 No Details →
4.9.0.80 31 Dec 2023 H2 U2 Apache-2.0 No Details →
4.8.1.78 28 Sep 2023 H2 U2 Apache-2.0 No Details →
4.8.0.76 09 Aug 2023 H1 U1 Apache-2.0 Yes Details →
4.8.0.74 30 Jun 2023 H1 U1 Apache-2.0 Yes Details →
4.7.0.72 22 Feb 2023 H1 U1 Apache-2.0 Yes Details →
4.7.0.68 30 Dec 2022 H1 U1 MIT Yes Details →
4.6.0.66 08 Jun 2022 H1 U1 MIT Yes Details →
3.4.18.65 08 Jun 2022 H5 M3 U8 MIT No Details →
3.4.17.63 09 Mar 2022 H5 M3 U8 MIT No Details →
4.5.5.64 09 Mar 2022 H1 U1 MIT Yes Details →
3.4.17.61 29 Dec 2021 H5 M3 U8 MIT No Details →
4.5.5.62 29 Dec 2021 H1 U1 MIT Yes Details →
3.4.16.59 22 Nov 2021 H5 M3 U8 MIT No Details →
4.5.4.60 22 Nov 2021 H1 U1 MIT Yes Details →
3.4.0.14 15 Nov 2021 H8 M5 U13 MIT No Details →
3.4.16.57 21 Oct 2021 H5 M3 U8 MIT No Details →
4.5.4.58 21 Oct 2021 H1 U1 MIT Yes Details →
4.5.3.56 11 Jul 2021 H1 U1 MIT Yes Details →
3.4.15.55 09 Jul 2021 H5 M3 U8 MIT No Details →
4.5.2.54 07 Jun 2021 H1 U1 MIT Yes Details →
3.4.14.53 07 Jun 2021 H5 M3 U8 MIT No Details →
3.4.14.51 07 May 2021 H5 M3 U8 MIT No Details →
4.5.2.52 07 May 2021 H1 U1 MIT Yes Details →
3.4.13.47 03 Jan 2021 H5 M3 U8 MIT No Details →
4.5.1.48 02 Jan 2021 H1 U1 MIT Yes Details →
4.4.0.46 03 Nov 2020 H1 U1 MIT Yes Details →
3.4.11.45 02 Nov 2020 H5 M3 U8 MIT No Details →
4.4.0.44 22 Sep 2020 H1 U1 MIT Yes Details →
3.4.11.43 22 Sep 2020 H5 M3 U8 MIT No Details →
4.4.0.42 16 Aug 2020 H1 U1 MIT Yes Details →
3.4.11.41 16 Aug 2020 H5 M3 U8 MIT No Details →
4.4.0.40 11 Aug 2020 H1 U1 MIT Yes Details →
3.4.11.39 11 Aug 2020 H5 M3 U8 MIT No Details →
4.3.0.38 09 Aug 2020 H1 U1 MIT Yes Details →
3.4.10.37 09 Aug 2020 H5 M3 U8 MIT No Details →
4.3.0.36 06 Jul 2020 H1 U1 MIT Yes Details →
3.4.10.35 05 Jul 2020 H5 M3 U8 MIT No Details →
4.2.0.34 04 Apr 2020 H1 U1 MIT Yes Details →
3.4.9.33 04 Apr 2020 H5 M3 U8 MIT No Details →
4.2.0.32 02 Feb 2020 H1 U1 MIT Yes Details →
3.4.9.31 01 Feb 2020 H5 M3 U8 MIT No Details →
4.1.2.30 21 Nov 2019 H2 U2 MIT Yes Details →
3.4.8.29 20 Nov 2019 H5 M3 U8 MIT No Details →
3.4.7.28 13 Sep 2019 H5 M3 U8 MIT No Details →
3.4.6.27 10 Sep 2019 H7 M3 U10 MIT No Details →
4.1.1.26 02 Sep 2019 H3 M1 U4 MIT No Details →
4.1.0.25 11 Apr 2019 H5 M2 U9 MIT No Details →
4.0.1.24 09 Apr 2019 H5 M3 U10 MIT No Details →
4.0.1.23 08 Apr 2019 H5 M3 U10 MIT No Details →
4.0.0.21 09 Jan 2019 H5 M3 U10 MIT No Details →
3.4.5.20 28 Dec 2018 H7 M3 U10 MIT No Details →
3.4.4.19 27 Nov 2018 H7 M3 U10 MIT No Details →
3.4.3.18 09 Sep 2018 H7 M3 U10 MIT No Details →
3.4.2.17 23 Jul 2018 H7 M3 U10 MIT No Details →
3.4.1.15 — H7 M3 U10 — No Details →

All 63 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 30
  • 2023 1
  • 2024 1
  • 2026 30

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 30 of the 62 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for opencv-python

The 5 most severe of 62 vulnerabilities recorded for this package

Search all 62 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About opencv-python

Is opencv-python safe to use?

Vulert records 62 vulnerabilities for opencv-python in PyPI: 0 critical, 23 high, 8 medium and 0 low, plus 31 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is opencv-python's Vulert package health score?

Vulert scores opencv-python 59/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of opencv-python affected?

Yes. 5.0.0.93, the version you would install today, has 4 known vulnerabilities, and 4 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of opencv-python should I use?

5.0.0.93 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does opencv-python have?

62 vulnerabilities are recorded for opencv-python in the PyPI ecosystem: 0 critical, 23 high, 8 medium and 0 low, plus 31 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new opencv-python vulnerabilities disclosed?

30 vulnerabilities were recorded for opencv-python in the last 12 months, and the oldest entry in this database dates to 12 Oct 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of opencv-python are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor opencv-python for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the opencv-python version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.