VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

wheel: vulnerability history, versions and safety

wheel is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 80 releases, from Dec 2022 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
4 vulnerabilities recorded H2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all wheel vulnerabilities

Vulert verdict on wheel 0.48.0 i

Updated on 23 Oct 2026

Good news: 0.48.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 0.48.0 — unaffected i
  • Vulnerabilities on record 4 over 3 years · 2 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 11,393 packages i
  • Stars 574 i
  • OpenSSF scorecard 4/10 i
  • Last release 2 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 wheel, 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.48.0 11 Aug 2026 none MIT — Details →
0.47.0 22 Apr 2026 none MIT — Details →
0.46.3 22 Jan 2026 none MIT — Details →
0.46.2 21 Jan 2026 none MIT — Details →
0.46.1 08 Apr 2025 H1 U1 MIT Yes Details →
0.46.0 03 Apr 2025 H1 U1 MIT Yes Details →
0.45.1 23 Nov 2024 H1 U1 MIT Yes Details →
0.45.0 08 Nov 2024 H1 U1 MIT Yes Details →
0.44.0 04 Aug 2024 H1 U1 MIT Yes Details →
0.43.0 11 Mar 2024 H1 U1 MIT Yes Details →
0.42.0 26 Nov 2023 H1 U1 MIT Yes Details →
0.41.3 30 Oct 2023 H1 U1 MIT Yes Details →
0.41.2 22 Aug 2023 H1 U1 MIT Yes Details →
0.41.1 05 Aug 2023 H1 U1 MIT Yes Details →
0.41.0 22 Jul 2023 H1 U1 MIT Yes Details →
0.40.0 14 Mar 2023 H1 U1 MIT Yes Details →
0.38.4 09 Nov 2022 H1 MIT Yes Details →
0.38.3 08 Nov 2022 H1 MIT Yes Details →
0.38.2 05 Nov 2022 H1 MIT Yes Details →
0.38.1 04 Nov 2022 H1 MIT Yes Details →
0.38.0 20 Oct 2022 H2 U1 MIT Yes Details →
0.37.1 22 Dec 2021 H2 U1 MIT Yes Details →
0.37.0 09 Aug 2021 H2 U1 MIT Yes Details →
0.36.2 13 Dec 2020 H2 U1 MIT Yes Details →
0.36.1 04 Dec 2020 H2 U1 MIT Yes Details →
0.36.0 01 Dec 2020 H2 U1 MIT Yes Details →
0.35.1 14 Aug 2020 H2 U1 MIT Yes Details →
0.35.0 13 Aug 2020 H2 U1 MIT Yes Details →
0.34.2 30 Jan 2020 H2 U1 MIT Yes Details →
0.34.1 27 Jan 2020 H2 U1 MIT Yes Details →
0.34.0 27 Jan 2020 H2 U1 MIT Yes Details →
0.33.6 18 Aug 2019 H2 U1 MIT Yes Details →
0.33.5 17 Aug 2019 H2 U1 MIT Yes Details →
0.33.4 11 May 2019 H2 U1 MIT Yes Details →
0.33.1 19 Feb 2019 H2 U1 MIT Yes Details →
0.33.0 12 Feb 2019 H2 U1 MIT Yes Details →
0.32.3 19 Nov 2018 H2 U1 MIT Yes Details →
0.32.2 20 Oct 2018 H2 U1 MIT Yes Details →
0.32.1 04 Oct 2018 H2 U1 MIT Yes Details →
0.32.0 29 Sep 2018 H2 U1 MIT Yes Details →
0.31.1 13 May 2018 H2 U1 MIT Yes Details →
0.31.0 01 Apr 2018 H2 U1 MIT Yes Details →
0.30.0 10 Sep 2017 H2 U1 MIT Yes Details →
0.30.0a0 14 Sep 2016 H2 U1 MIT Yes Details →
0.29.0 06 Feb 2016 H2 U1 MIT Yes Details →
0.28.0 05 Feb 2016 H2 U1 MIT Yes Details →
0.27.0 05 Feb 2016 H2 U1 MIT Yes Details →
0.26.0 18 Sep 2015 H2 U1 MIT Yes Details →
0.25.0 17 Sep 2015 H2 U1 MIT Yes Details →
0.24.0 06 Jul 2014 H2 U1 MIT Yes Details →
0.23.0 01 Apr 2014 H2 U1 MIT Yes Details →
0.22.0 15 Sep 2013 H2 U1 MIT Yes Details →
0.21.0 20 Jul 2013 H2 U1 MIT Yes Details →
0.19.0 19 Jul 2013 H2 U1 MIT Yes Details →
0.18.0 04 Jul 2013 H2 U1 MIT Yes Details →
0.17.0 23 Jun 2013 H2 U1 MIT Yes Details →
0.16.0 30 Apr 2013 H2 U1 MIT Yes Details →
0.15.0 15 Jan 2013 H2 U1 MIT Yes Details →
0.14.0 27 Oct 2012 H2 U1 MIT Yes Details →
0.13.0 18 Oct 2012 H2 U1 MIT Yes Details →
0.12.0 06 Oct 2012 H2 U1 MIT Yes Details →
0.11.0 06 Oct 2012 H2 U1 MIT Yes Details →
0.10.3 03 Oct 2012 H2 U1 MIT Yes Details →
0.10.2 03 Oct 2012 H2 U1 MIT Yes Details →
0.10.1 01 Oct 2012 H2 U1 MIT Yes Details →
0.10.0 01 Oct 2012 H2 U1 MIT Yes Details →
0.9.7 20 Sep 2012 H2 U1 MIT Yes Details →
0.9.6 20 Sep 2012 H2 U1 MIT Yes Details →
0.9.5 16 Sep 2012 H2 U1 MIT Yes Details →
0.9.4 11 Sep 2012 H2 U1 MIT Yes Details →
0.9.3 11 Sep 2012 H2 U1 MIT Yes Details →
0.9.2 29 Aug 2012 H2 U1 MIT Yes Details →
0.9.1 28 Aug 2012 H2 U1 MIT Yes Details →
0.9.0 23 Aug 2012 H2 U1 MIT Yes Details →
0.8.0 17 Aug 2012 H2 U1 MIT Yes Details →
0.7.0 28 Jul 2012 H2 U1 MIT Yes Details →
0.6.0 23 Jul 2012 H2 U1 MIT Yes Details →
0.5.0 17 Jul 2012 H2 U1 MIT Yes Details →
0.4.2 12 Jul 2012 H2 U1 MIT Yes Details →
0.4.1 12 Jul 2012 H2 U1 MIT Yes Details →
0.4.0 12 Jul 2012 H2 U1 MIT Yes Details →
0.3.0 05 Jul 2012 H2 U1 MIT Yes Details →
0.2.0 03 Jul 2012 H2 U1 MIT Yes Details →
0.1.0 01 Jul 2012 H2 U1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for wheel

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-40898: pypa/wheel Regular Expression Denial of Service (ReDoS) 7.5 high 0.38.1 23 Dec 2022
CVE-2026-24049: Wheel Package Vulnerability Leading to Arbitrary File Permission Modification 7.1 high 0.46.2 22 Jan 2026
CVE-2026-24049: Wheel Package Vulnerability Leading to Arbitrary File Permission Modification 7.1 high 0.46.2 07 Jul 2026
CVE-2022-40898: Denial of Service Vulnerability in Python Packaging Authority (PyPA) Wheel N/A unrated 0.38.1 23 Dec 2022

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 wheel

Is wheel safe to use?

Vulert records 4 vulnerabilities for wheel in PyPI: 0 critical, 2 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is wheel's Vulert package health score?

Vulert scores wheel 78/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 wheel affected?

No. 0.48.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 wheel should I use?

0.48.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 wheel have?

4 vulnerabilities are recorded for wheel in the PyPI ecosystem: 0 critical, 2 high, 0 medium and 0 low, plus 2 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 wheel vulnerabilities disclosed?

2 vulnerabilities were recorded for wheel in the last 12 months, and the oldest entry in this database dates to 23 Dec 2022. 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 wheel 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 wheel for upcoming vulnerabilities?

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