Skip to content
Fencer Vulns
high 7.5

CVE-2025-62370 json

Alloy Core has a DoS vulnerability on `alloy_dyn_abi::TypedData` hashing

published 2025-10-15 12 mo ago modified 2026-10-12 27 d ago also GHSA-pgp9-98jm-wwq2 , RUSTSEC-2025-0073 , EUVD-2025-34683

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

Alloy Core libraries at the root of the Rust Ethereum ecosystem. Prior to 0.8.26 and 1.4.1, an uncaught panic triggered by malformed input to alloy_dyn_abi::TypedData could lead to a denial-of-service (DoS) via eip712_signing_hash(). Software with high availability requirements such as network services may be particularly impacted. If in use, external auto-restarting mechanisms can partially mitigate the availability issues unless repeated attacks are possible. The vulnerability was patched by adding a check to ensure the element is not empty before accessing its first element; an error is returned if it is empty. The fix is included in version v1.4.1 and backported to v0.8.26.

Patch / fix

  • crates.io alloy-dyn-abi 0.8.26, 1.4.1
  • cargo-audit-advisory-db openSUSE Tumbleweed 20251021-1.1

opensuse advisories openSUSE-SU-2025:15652-1

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
12 mo ago

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
crates.io alloy-dyn-abi
<0.8.26
>=1.0.0, <1.4.1
>=0.0.0-0, <0.8.26
0.8.26
1.4.1

Affected products

  • alloy-rs core

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.