VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

py-evm: vulnerability history, versions and safety

py-evm is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 88 releases, first recorded in Nov 2018. 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 H1 U1
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 py-evm vulnerabilities

Vulert verdict on py-evm 0.12.1b1 i

Updated on 23 Oct 2026

Careful: 0.12.1b1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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 0.12.1b1 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 21 Nov 2018 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Depended on by 113 packages i
  • Stars 2,349 i
  • OpenSSF scorecard 1/10 i
  • Last release 17 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 py-evm, 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.12.1b1 14 May 2025 H1 MIT No Details →
0.12.0b3 25 Apr 2025 H1 MIT No Details →
0.12.0b2 23 Apr 2025 H1 MIT No Details →
0.12.0b1 21 Apr 2025 H1 MIT No Details →
0.11.0b1 18 Feb 2025 H1 MIT No Details →
0.10.1b2 21 Aug 2024 H1 MIT No Details →
0.10.1b1 18 Apr 2024 H1 MIT No Details →
0.10.0b6 05 Apr 2024 H1 MIT No Details →
0.10.0b5 05 Apr 2024 H1 MIT No Details →
0.10.0b4 18 Mar 2024 H1 MIT No Details →
0.10.0b3 18 Mar 2024 H1 MIT No Details →
0.10.0b2 15 Mar 2024 H1 MIT No Details →
0.10.0b1 15 Mar 2024 H1 MIT No Details →
0.9.0b1 05 Feb 2024 H1 MIT No Details →
0.8.0b1 09 Oct 2023 H1 MIT No Details →
0.7.0a4 24 Jul 2023 H1 MIT No Details →
0.7.0a3 08 Jun 2023 H1 MIT No Details →
0.7.0a2 11 May 2023 H1 MIT No Details →
0.7.0a1 10 Apr 2023 H1 MIT No Details →
0.6.1a2 16 Dec 2022 H1 MIT No Details →
0.6.1a1 14 Nov 2022 H1 MIT No Details →
0.6.0a1 22 Aug 2022 H1 MIT No Details →
0.5.0a3 26 Jan 2022 H1 MIT No Details →
0.5.0a2 17 Dec 2021 H1 MIT No Details →
0.5.0a1 13 Oct 2021 H1 MIT No Details →
0.5.0a0 30 Sep 2021 H1 MIT No Details →
0.4.0a4 07 Apr 2021 H1 MIT No Details →
0.4.0a3 24 Mar 2021 H1 MIT No Details →
0.4.0a2 22 Mar 2021 H1 MIT No Details →
0.4.0a1 22 Mar 2021 H1 MIT No Details →
0.3.0a20 21 Oct 2020 H1 MIT No Details →
0.3.0a19 31 Aug 2020 H1 MIT No Details →
0.3.0a18 25 Jun 2020 H1 MIT No Details →
0.3.0a17 02 Jun 2020 H1 MIT No Details →
0.3.0a16 27 May 2020 H1 MIT No Details →
0.3.0a15 14 Apr 2020 H1 MIT No Details →
0.3.0a14 10 Feb 2020 H1 MIT No Details →
0.3.0a13 13 Jan 2020 H1 MIT No Details →
0.3.0a12 19 Dec 2019 H1 MIT No Details →
0.3.0a11 12 Dec 2019 H1 MIT No Details →
0.3.0a10 10 Dec 2019 H1 MIT No Details →
0.3.0a9 02 Dec 2019 H1 MIT No Details →
0.3.0a8 05 Nov 2019 H1 MIT No Details →
0.3.0a7 19 Sep 2019 H1 MIT No Details →
0.3.0a6 05 Sep 2019 H1 MIT No Details →
0.3.0a5 22 Aug 2019 H1 MIT No Details →
0.3.0a4 19 Aug 2019 H1 MIT No Details →
0.3.0a3 13 Aug 2019 H1 MIT No Details →
0.3.0a2 13 Aug 2019 H1 MIT No Details →
0.3.0a1 06 Jun 2019 H1 MIT No Details →
0.2.0a43 20 May 2019 H1 MIT No Details →
0.2.0a42 28 Feb 2019 H1 MIT No Details →
0.2.0a41 16 Jan 2019 H1 MIT No Details →
0.2.0a40 15 Jan 2019 H1 MIT No Details →
0.2.0a39 10 Jan 2019 H1 MIT No Details →
0.2.0a38 20 Dec 2018 H1 MIT No Details →
0.2.0a37 13 Dec 2018 H1 MIT No Details →
0.2.0a36 13 Dec 2018 H1 MIT No Details →
0.2.0a35 13 Dec 2018 H1 MIT No Details →
0.2.0a34 20 Nov 2018 H1 MIT No Details →
0.2.0a33 27 Sep 2018 H1 MIT No Details →
0.2.0a32 04 Sep 2018 H1 U1 MIT No Details →
0.2.0a31 14 Aug 2018 H1 U1 MIT No Details →
0.2.0a30 08 Aug 2018 H1 U1 MIT No Details →
0.2.0a29 24 Jul 2018 H1 U1 MIT No Details →
0.2.0a28 24 Jul 2018 H1 U1 MIT No Details →
0.2.0a26 01 Jun 2018 H1 U1 MIT No Details →
0.2.0a25 01 Jun 2018 H1 U1 MIT No Details →
0.2.0a24 01 Jun 2018 H1 U1 MIT No Details →
0.2.0a22 01 Jun 2018 H1 U1 MIT No Details →
0.2.0a21 31 May 2018 H1 U1 MIT No Details →
0.2.0a20 30 May 2018 H1 U1 MIT No Details →
0.2.0a19 29 May 2018 H1 U1 MIT No Details →
0.2.0a18 17 May 2018 H1 U1 MIT No Details →
0.2.0a17 09 May 2018 H1 U1 MIT No Details →
0.2.0a16 01 May 2018 H1 U1 MIT No Details →
0.2.0a15 19 Apr 2018 H1 U1 MIT No Details →
0.2.0a14 03 Apr 2018 H1 U1 MIT No Details →
0.2.0a13 02 Apr 2018 H1 U1 MIT No Details →
0.2.0a12 08 Mar 2018 H1 U1 MIT No Details →
0.2.0a11 22 Feb 2018 H1 U1 MIT No Details →
0.2.0a10 24 Jan 2018 H1 U1 MIT No Details →
0.2.0a9 17 Jan 2018 H1 U1 MIT No Details →
0.2.0a8 04 Jan 2018 H1 U1 MIT No Details →
0.2.0a7 30 Nov 2017 H1 U1 MIT No Details →
0.2.0a5 29 Sep 2017 H1 U1 MIT No Details →
0.2.0a3 29 Sep 2017 H1 U1 MIT No Details →
0.2.0a1 24 Aug 2017 H1 U1 MIT No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2

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 py-evm

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-18920: py-evm - Improper Restriction of Operations within the Bounds of a Memory Buffer 8.8 high No fix published 21 Nov 2018
CVE-2018-18920: py-evm - Smart Contract Execution Failure N/A unrated 0.2.0a33 12 Nov 2018

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 py-evm

Is py-evm safe to use?

Vulert records 2 vulnerabilities for py-evm in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is py-evm's Vulert package health score?

Vulert scores py-evm 60/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 py-evm affected?

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

Which version of py-evm should I use?

0.12.1b1 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 py-evm have?

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

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

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