evm-core (cargo) has 2 known vulnerabilities, the worst rated MODERATE. Upgrade to 0.26.1 or later to clear all of them. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
0 packages depend on it
dependents not yet indexed for this ecosystem
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so cargo packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 70th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-4jwq-572w-4388, the advisory selected below
Prior to the patch, when executing specific EVM opcodes related to memory operations that use evmcore::Memory::copylarge, the crate can over-allocate memory…
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for evm-core (cargo), the worst rated MODERATE, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 2 known vulnerabilities for evm-core (cargo), the worst rated MODERATE. They are GHSA-4jwq-572w-4388, GHSA-773q-5334-5gf9.
0.26.1 or later clears every advisory recorded for evm-core (cargo). Check the release you pick before installing it.
Search evm-core in CyberXYZ Check at https://cyberxyz.io/check?q=evm-core. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 06:18 UTC. The most recent advisory here was published 2024-01-30. Updated continuously from NVD, GHSA, OSV and CNA feeds.