VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

web3: vulnerability history, versions and safety

web3 is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 72 releases, from Apr 2026 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
2 vulnerabilities recorded M1 U1
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 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all web3 vulnerabilities

Vulert verdict on web3 8.0.0 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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

  • Current release 8.0.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 7.2 i
  • With no published fix 0 i
  • Depended on by 853 packages i
  • Stars 5,546 i
  • Last release 1 month ago i
  • Licence MIT 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 web3, 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
8.0.0 31 Aug 2026 none MIT — Details →
7.16.0 01 May 2026 none MIT — Details →
8.0.0b3 30 Apr 2026 none MIT — Details →
8.0.0b2 02 Apr 2026 none MIT — Details →
7.15.0 02 Apr 2026 none MIT — Details →
7.14.1 03 Feb 2026 M1 U1 MIT Yes Details →
8.0.0b1 19 Dec 2025 U1 MIT Yes Details →
7.14.0 16 Oct 2025 M1 U1 MIT Yes Details →
7.13.0 04 Aug 2025 M1 U1 MIT Yes Details →
7.12.1 14 Jul 2025 M1 U1 MIT Yes Details →
7.12.0 22 May 2025 M1 U1 MIT Yes Details →
7.11.1 12 May 2025 M1 U1 MIT Yes Details →
7.11.0 29 Apr 2025 M1 U1 MIT Yes Details →
7.10.0 27 Mar 2025 M1 U1 MIT Yes Details →
7.9.0 12 Mar 2025 M1 U1 MIT Yes Details →
6.20.4 19 Feb 2025 M1 U1 MIT Yes Details →
7.8.0 03 Feb 2025 M1 U1 MIT Yes Details →
7.7.0 15 Jan 2025 M1 U1 MIT Yes Details →
7.6.1 18 Dec 2024 M1 U1 MIT Yes Details →
7.6.0 22 Nov 2024 M1 U1 MIT Yes Details →
7.5.0 06 Nov 2024 M1 U1 MIT Yes Details →
7.4.0 16 Oct 2024 M1 U1 MIT Yes Details →
7.3.1 14 Oct 2024 M1 U1 MIT Yes Details →
7.3.0 25 Sep 2024 M1 U1 MIT Yes Details →
7.2.0 29 Aug 2024 M1 U1 MIT Yes Details →
7.1.0 28 Aug 2024 M1 U1 MIT Yes Details →
6.20.3 22 Aug 2024 M1 U1 MIT Yes Details →
7.0.0 21 Aug 2024 M1 U1 MIT Yes Details →
6.20.2 14 Aug 2024 M1 U1 MIT Yes Details →
7.0.0b9 01 Aug 2024 M1 U1 MIT Yes Details →
7.0.0b8 24 Jul 2024 M1 U1 MIT Yes Details →
6.20.1 22 Jul 2024 M1 U1 MIT Yes Details →
6.20.0 26 Jun 2024 M1 U1 MIT Yes Details →
7.0.0b7 26 Jun 2024 M1 U1 MIT Yes Details →
7.0.0b6 15 May 2024 M1 U1 MIT Yes Details →
6.19.0 15 May 2024 M1 U1 MIT Yes Details →
6.18.0 29 Apr 2024 M1 U1 MIT Yes Details →
7.0.0b5 26 Apr 2024 M1 U1 MIT Yes Details →
6.17.2 17 Apr 2024 M1 U1 MIT Yes Details →
6.17.1 15 Apr 2024 M1 U1 MIT Yes Details →
6.17.0 11 Apr 2024 M1 U1 MIT Yes Details →
7.0.0b4 11 Apr 2024 M1 U1 MIT Yes Details →
6.16.0 28 Mar 2024 M1 U1 MIT Yes Details →
7.0.0b3 28 Mar 2024 M1 U1 MIT Yes Details →
7.0.0b2 12 Mar 2024 M1 U1 MIT Yes Details →
7.0.0b1 28 Feb 2024 M1 U1 MIT Yes Details →
6.15.1 05 Feb 2024 M1 U1 MIT Yes Details →
6.15.0 25 Jan 2024 M1 U1 MIT Yes Details →
6.14.0 10 Jan 2024 M1 U1 MIT Yes Details →
6.13.0 20 Dec 2023 M1 U1 MIT Yes Details →
6.12.0 11 Dec 2023 M1 U1 MIT Yes Details →
6.11.4 27 Nov 2023 M1 U1 MIT Yes Details →
6.11.3 08 Nov 2023 M1 U1 MIT Yes Details →
6.11.2 30 Oct 2023 M1 U1 MIT Yes Details →
6.11.1 18 Oct 2023 M1 U1 MIT Yes Details →
6.11.0 11 Oct 2023 M1 U1 MIT Yes Details →
6.10.0 21 Sep 2023 M1 U1 MIT Yes Details →
6.9.0 23 Aug 2023 M1 U1 MIT Yes Details →
6.8.0 02 Aug 2023 M1 U1 MIT Yes Details →
6.7.0 26 Jul 2023 M1 U1 MIT Yes Details →
6.6.1 12 Jul 2023 M1 U1 MIT Yes Details →
6.6.0 12 Jul 2023 M1 U1 MIT Yes Details →
6.5.0 15 Jun 2023 M1 U1 MIT Yes Details →
6.4.0 15 May 2023 M1 U1 MIT Yes Details →
6.3.0 03 May 2023 M1 U1 MIT Yes Details →
6.2.0 12 Apr 2023 M1 U1 MIT Yes Details →
6.1.0 05 Apr 2023 M1 U1 MIT Yes Details →
6.0.0 14 Mar 2023 M1 U1 MIT Yes Details →
5.31.4 13 Mar 2023 none MIT — Details →
6.0.0b11 24 Feb 2023 M1 U1 MIT Yes Details →
6.0.0b10 15 Feb 2023 M1 U1 MIT Yes Details →
6.0.0b9 03 Jan 2023 M1 U1 MIT Yes Details →
5.31.3 02 Dec 2022 none MIT — Details →
5.31.2 01 Dec 2022 none MIT — Details →
6.0.0b8 14 Nov 2022 M1 U1 MIT Yes Details →
6.0.0b7 19 Oct 2022 M1 U1 MIT Yes Details →
5.31.1 06 Oct 2022 none MIT — Details →
6.0.0b6 26 Sep 2022 M1 U1 MIT Yes Details →
5.31.0 19 Sep 2022 none MIT — Details →
6.0.0b5 19 Sep 2022 M1 U1 MIT Yes Details →
6.0.0b4 13 Jul 2022 M1 U1 MIT Yes Details →
5.30.0 07 Jul 2022 none MIT — Details →
5.29.2 01 Jun 2022 none MIT — Details →
6.0.0b3 01 Jun 2022 M1 U1 MIT Yes Details →
5.29.1 16 May 2022 none MIT — Details →
6.0.0b2 27 Apr 2022 none MIT — Details →
5.29.0 13 Apr 2022 none MIT — Details →
6.0.0b1 28 Feb 2022 none MIT — Details →
5.28.0 09 Feb 2022 none MIT — Details →
5.27.0 31 Jan 2022 none MIT — Details →
5.26.0 06 Jan 2022 none MIT — Details →
5.25.0 19 Nov 2021 none MIT — Details →
5.24.0 27 Sep 2021 none MIT — Details →
5.23.1 27 Aug 2021 none MIT — Details →
5.23.0 12 Aug 2021 none MIT — Details →
5.22.0 02 Aug 2021 none MIT — Details →
5.21.0 12 Jul 2021 none MIT — Details →
5.20.1 01 Jul 2021 none MIT — Details →
5.20.0 09 Jun 2021 none MIT — Details →
5.19.0 28 Apr 2021 none MIT — Details →
5.18.0 09 Apr 2021 none — — Details →
5.17.0 24 Feb 2021 none — — Details →
5.16.0 04 Feb 2021 none — — Details →
5.15.0 15 Jan 2021 none — — Details →
5.14.0 05 Jan 2021 none — — Details →
5.13.1 03 Dec 2020 none — — Details →
5.13.0 29 Oct 2020 none — — Details →
5.12.3 21 Oct 2020 none — — Details →
5.12.2 12 Oct 2020 none — — Details →
5.12.1 02 Sep 2020 none — — Details →
5.12.0 20 Jul 2020 none — — Details →
5.12.0b3 15 Jul 2020 none — — Details →
5.12.0b2 14 Jul 2020 none — — Details →
5.12.0b1 09 Jul 2020 none — — Details →
5.11.1 17 Jun 2020 none — — Details →
5.11.0 03 Jun 2020 none — — Details →
5.10.0 18 May 2020 none — — Details →
5.9.0 30 Apr 2020 none — — Details →
5.8.0 23 Apr 2020 none — — Details →
5.7.0 16 Mar 2020 none — — Details →

The newest 120 of 252 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for web3

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-40072: web3.py SSRF Vulnerability via CCIP Read OffchainLookup URL Handling 7.2 high 7.15.0 13 Jul 2026
Server-Side Request Forgery (SSRF) Vulnerability in web3.py: CCIP Read URL Handling 6.9 medium 7.15.0 04 Apr 2026

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 web3

Is web3 safe to use?

Vulert records 2 vulnerabilities for web3 in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 web3's Vulert package health score?

Vulert scores web3 87/100, which reads as healthy. 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 web3 affected?

No. 8.0.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 web3 should I use?

8.0.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 web3 have?

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

2 vulnerabilities were recorded for web3 in the last 12 months, and the oldest entry in this database dates to 04 Apr 2026. 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 web3 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 web3 for upcoming vulnerabilities?

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