VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

scikit-image: vulnerability history, versions and safety

scikit-image is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all scikit-image vulnerabilities

Vulert verdict on scikit-image 0.26.0 i

Updated on 23 Oct 2026

Good news: 0.26.0, the version you would install today, has no known vulnerabilities.

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

What to do: Stay on 0.26.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.26.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.26.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 7,060 packages i
  • Stars 6,624 i
  • OpenSSF scorecard 3/10 i
  • Last release 10 months ago i
  • Licence non-standard 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 scikit-image, 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
0.26.0 20 Dec 2025 none non-standard — Details →
0.26.0rc2 18 Dec 2025 none non-standard — Details →
0.26.0rc1 09 Dec 2025 none non-standard — Details →
0.26.0rc0 26 Nov 2025 none non-standard — Details →
0.25.2 18 Feb 2025 none non-standard — Details →
0.25.2rc0 15 Feb 2025 none non-standard — Details →
0.25.1 26 Jan 2025 none non-standard — Details →
0.25.0 13 Dec 2024 none non-standard — Details →
0.25.0rc2 10 Dec 2024 none non-standard — Details →
0.25.0rc1 07 Oct 2024 none non-standard — Details →
0.25.0rc0 06 Oct 2024 none non-standard — Details →
0.24.0 18 Jun 2024 none non-standard — Details →
0.24.0rc1 16 Jun 2024 none non-standard — Details →
0.23.2 20 Apr 2024 none non-standard — Details →
0.23.2rc1 14 Apr 2024 none non-standard — Details →
0.23.1 10 Apr 2024 none non-standard — Details →
0.23.0 10 Apr 2024 none non-standard — Details →
0.23.0rc2 04 Apr 2024 none non-standard — Details →
0.23.0rc0 22 Mar 2024 none non-standard — Details →
0.22.0 03 Oct 2023 none non-standard — Details →
0.22.0rc1 30 Sep 2023 none non-standard — Details →
0.21.0 02 Jun 2023 none non-standard — Details →
0.21.0rc1 18 May 2023 none non-standard — Details →
0.21.0rc0 12 Apr 2023 none non-standard — Details →
0.20.0 28 Feb 2023 none non-standard — Details →
0.20.0rc8 20 Feb 2023 none non-standard — Details →
0.20.0rc7 17 Feb 2023 none non-standard — Details →
0.20.0rc6 16 Feb 2023 none non-standard — Details →
0.20.0rc5 13 Feb 2023 none non-standard — Details →
0.20.0rc4 07 Feb 2023 none non-standard — Details →
0.20.0rc3 02 Feb 2023 none non-standard — Details →
0.20.0rc2 01 Feb 2023 none non-standard — Details →
0.20.0.dev0 01 Feb 2023 none non-standard — Details →
0.19.3 12 Jun 2022 none non-standard — Details →
0.19.2 17 Feb 2022 none non-standard — Details →
0.19.1 15 Dec 2021 none non-standard — Details →
0.19.0 03 Dec 2021 none non-standard — Details →
0.19.0rc0 22 Nov 2021 none non-standard — Details →
0.18.3 24 Aug 2021 none non-standard — Details →
0.18.2 29 Jun 2021 none non-standard — Details →
0.18.1 23 Dec 2020 none non-standard — Details →
0.18.0 15 Dec 2020 none non-standard — Details →
0.17.2 13 May 2020 none non-standard — Details →
0.17.1 08 May 2020 none non-standard — Details →
0.16.2 27 Nov 2019 none non-standard — Details →
0.16.1 14 Oct 2019 none non-standard — Details →
0.14.5 10 Sep 2019 none non-standard — Details →
0.14.4 04 Sep 2019 none non-standard — Details →
0.14.3 12 Jun 2019 none non-standard — Details →
0.15.0 03 Apr 2019 none non-standard — Details →
0.14.2 18 Jan 2019 none non-standard — Details →
0.14.1 02 Oct 2018 none non-standard — Details →
0.14.0 16 Aug 2018 none non-standard — Details →
0.13.1 28 Sep 2017 none non-standard — Details →
0.13.0 29 Mar 2017 none non-standard — Details →
0.12.3 08 Mar 2016 none non-standard — Details →
0.12.2 07 Mar 2016 none non-standard — Details →
0.12.1 07 Mar 2016 none non-standard — Details →
0.12.0 07 Mar 2016 none non-standard — Details →
0.11.3 01 Apr 2015 none non-standard — Details →
0.11.2 05 Mar 2015 none non-standard — Details →
0.10.1 30 Jun 2014 none non-standard — Details →
0.10.0 28 May 2014 none non-standard — Details →
0.9.3 27 Oct 2013 none non-standard — Details →
0.9.1 19 Oct 2013 none non-standard — Details →
0.9.0 19 Oct 2013 none non-standard — Details →
0.8.2 06 Mar 2013 none non-standard — Details →
0.8.1 06 Mar 2013 none non-standard — Details →
0.8.0 04 Mar 2013 none non-standard — Details →
0.7.2 14 Oct 2012 none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for scikit-image

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 scikit-image

Is scikit-image safe to use?

Vulert has no vulnerabilities on record for scikit-image in PyPI at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is scikit-image's Vulert package health score?

Vulert scores scikit-image 81/100, which reads as in good shape. 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).

Is the latest version of scikit-image affected?

No. 0.26.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of scikit-image should I use?

0.26.0 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 scikit-image have?

0 vulnerabilities are recorded for scikit-image in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new scikit-image vulnerabilities disclosed?

0 vulnerabilities were recorded for scikit-image in the last 12 months. 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 scikit-image 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 scikit-image for upcoming vulnerabilities?

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