Advisory record · GHSA-773q-5334-5gf9

Memory over-allocation in evm-core

No CVSS score

Published by the GitHub Advisory Database at 25 Aug 2021, 20:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
evm-corecrates.io>=0.26.0, <0.26.1 || >=0.25.0, <0.25.1 || >=0.24.0, <0.24.1 || >=0.23.0, <0.23.1 || <0.21.10.26.1, 0.25.1, 0.24.1, 0.23.1, 0.21.1
Identifiers
GHSA-773q-5334-5gf9 · RUSTSEC-2021-0066
Weakness (CWE)
CWE-789
Published
25 Aug 2021
Updated
8 Nov 2023

Machine-written summary

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

Vulnerable versions of the evm-core crate before 0.21.1, from 0.23.0 before 0.23.1, from 0.24.0 before 0.24.1, from 0.25.0 before 0.25.1, and from 0.26.0 before 0.26.1 can over-allocate memory when running certain EVM memory opcodes that use copy_large. An attacker who can get such opcodes executed can cause a denial of service. Upgrade to 0.21.1, 0.23.1, 0.24.1, 0.25.1, or 0.26.1, matching your release line. The source gives few details about which opcodes trigger it.

Written 9 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

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:20 UTC First seen by agentprime
  2. 31 Oct 2026, 15:20 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.