Advisory record · GHSA-4jwq-572w-4388

Memory over-allocation in evm crate

CVSS 6.5 MediumEPSS 0.013 · 70th percentile

Published by the GitHub Advisory Database at 30 Jan 2024, 23:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
evmcrates.io<0.21.1 || >=0.22.0, <0.22.1 || >=0.23.0, <0.23.1 || >=0.24.0, <0.24.1 || >=0.25.0, <0.25.1 || >=0.26.0, <0.26.10.21.1, 0.22.1, 0.23.1, 0.24.1, 0.25.1, 0.26.1
evm-corecrates.io<0.21.1 || >=0.22.0, <0.22.1 || >=0.23.0, <0.23.1 || >=0.24.0, <0.24.1 || >=0.25.0, <0.25.1 || >=0.26.0, <0.26.10.21.1, 0.22.1, 0.23.1, 0.24.1, 0.25.1, 0.26.1
Identifiers
GHSA-4jwq-572w-4388 · CVE-2021-29511
Weakness (CWE)
CWE-770 · CWE-787
Published
30 Jan 2024
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Two packages, evm and evm-core, are affected in versions below 0.21.1, 0.22.0 up to 0.22.1, 0.23.0 up to 0.23.1, 0.24.0 up to 0.24.1, 0.25.0 up to 0.25.1, and 0.26.0 up to 0.26.1. When executing certain memory-related EVM opcodes, the crate can allocate more memory than needed, which lets an attacker cause a denial of service. Upgrade evm or evm-core to 0.21.1, 0.22.1, 0.23.1, 0.24.1, 0.25.1, or 0.26.1 or later; no workaround is listed.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.013, the 70th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:18 UTC First seen by agentprime
  2. 31 Oct 2026, 15:18 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.