VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

eth-abi: vulnerability history, versions and safety

eth-abi is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 35 releases, from Nov 2023 to Mar 2024. 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 M2
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 eth-abi vulnerabilities

Vulert verdict on eth-abi 6.0.0 i

Updated on 23 Oct 2026

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

Package health score 89/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 6.0.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 05 Mar 2024 i
  • Highest CVSS 4.3 i
  • With no published fix 0 i
  • Depended on by 1,679 packages i
  • Stars 256 i
  • Last release 2 months 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 eth-abi, 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
6.0.0 22 Aug 2026 none MIT — Details →
6.0.0b1 17 Dec 2025 none MIT — Details →
5.2.0 14 Jan 2025 none MIT — Details →
5.1.0 01 Apr 2024 none MIT — Details →
5.0.1 04 Mar 2024 none MIT — Details →
5.0.0 10 Jan 2024 M1 MIT Yes Details →
4.2.1 13 Sep 2023 M1 MIT Yes Details →
4.2.0 28 Aug 2023 M1 MIT Yes Details →
4.1.0 08 Jun 2023 M2 MIT Yes Details →
4.0.0 22 Mar 2023 M2 MIT Yes Details →
4.0.0b3 20 Mar 2023 M2 MIT Yes Details →
4.0.0b2 22 Nov 2022 M2 MIT Yes Details →
4.0.0b1 27 Sep 2022 M2 MIT Yes Details →
2.2.0 20 Jul 2022 M2 MIT Yes Details →
3.0.1 18 Jul 2022 M2 MIT Yes Details →
3.0.0 19 Jan 2022 M2 MIT Yes Details →
2.1.1 27 Feb 2020 M2 MIT Yes Details →
2.1.0 10 Dec 2019 M2 MIT Yes Details →
2.0.0 11 Jul 2019 M2 MIT Yes Details →
2.0.0b9 20 May 2019 M2 MIT Yes Details →
2.0.0b8 30 Mar 2019 M2 MIT Yes Details →
2.0.0b7 24 Mar 2019 M2 MIT Yes Details →
2.0.0b6 21 Feb 2019 M2 MIT Yes Details →
2.0.0b5 22 Jan 2019 M2 MIT Yes Details →
2.0.0b4 20 Dec 2018 M2 MIT Yes Details →
2.0.0b3 06 Dec 2018 M2 MIT Yes Details →
1.3.0 06 Dec 2018 M2 MIT Yes Details →
1.2.2 18 Oct 2018 M2 MIT Yes Details →
2.0.0b2 16 Oct 2018 M2 MIT Yes Details →
1.2.1 16 Oct 2018 M2 MIT Yes Details →
2.0.0b1 30 Aug 2018 M2 MIT Yes Details →
2.0.0b0 30 Aug 2018 M2 MIT Yes Details →
1.2.0 28 Aug 2018 M2 MIT Yes Details →
2.0.0a1 20 Jul 2018 M2 MIT Yes Details →
1.1.1 10 May 2018 M2 MIT Yes Details →
1.1.0 08 May 2018 M2 MIT Yes Details →
1.0.0 01 Mar 2018 M2 MIT Yes Details →
1.0.0b1 21 Feb 2018 M2 MIT Yes Details →
1.0.0b0 05 Feb 2018 M2 MIT Yes Details →
0.5.0 23 Nov 2017 M2 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for eth-abi

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Ethereum ABI decoder Denial-of-Service (DoS) Vulnerability in eth-abi 4.3 medium 4.2.0 24 Nov 2023
eth-abi is vulnerable to recursive DoS N/A medium 5.0.1 05 Mar 2024

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 eth-abi

Is eth-abi safe to use?

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

What is eth-abi's Vulert package health score?

Vulert scores eth-abi 89/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 eth-abi affected?

No. 6.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 eth-abi should I use?

6.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 eth-abi have?

2 vulnerabilities are recorded for eth-abi in the PyPI ecosystem: 0 critical, 0 high, 2 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 eth-abi vulnerabilities disclosed?

0 vulnerabilities were recorded for eth-abi in the last 12 months, and the oldest entry in this database dates to 24 Nov 2023. 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 eth-abi 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 eth-abi for upcoming vulnerabilities?

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