CVE-2025-62370: Alloy Core has a DoS vulnerability on `alloy_dyn_abi::TypedData` hashing

Published Oct 15, 2025
·
Updated

Impact

An uncaught panic triggered by malformed input to alloydynabi::TypedData could lead to a denial-of-service (DoS) via eip712signinghash().

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.

Patches

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.

Workarounds

There is no known workaround that mitigates the vulnerability. Upgrading to a patched version is the recommended course of action.

Reported by

Christian Reitter & Zeke Mostov from Turnkey

Other sources

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 alloydynabi::TypedData could lead to a denial-of-service (DoS) via eip712signinghash(). 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.

MITRE

Affected Software

3 affected componentsFixes available
ALLOY Core<0.8.26, <1.4.1
rust/alloy-dyn-abi>=1.0.0<1.4.1
1.4.1
rust/alloy-dyn-abi<0.8.26
0.8.26

Event History

Oct 15, 2025
CVE Published
via MITRE·03:32 PM
Data Sourced
via MITRE·03:32 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·05:27 PM
Data Sourced
via GitHub·05:27 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-62370?

CVE-2025-62370 has a severity that could result in a denial-of-service due to uncaught panics from malformed input.

2

How do I fix CVE-2025-62370?

To fix CVE-2025-62370, update to Alloy Core versions 0.8.26 or later, or 1.4.1 or later.

3

What software is affected by CVE-2025-62370?

CVE-2025-62370 affects Alloy Core versions prior to 0.8.26 and 1.4.1.

4

What could happen if CVE-2025-62370 is exploited?

Exploiting CVE-2025-62370 could lead to a denial-of-service (DoS) condition in the affected software.

5

What kind of attack does CVE-2025-62370 relate to?

CVE-2025-62370 relates to denial-of-service attacks caused by uncaught panics from malformed input.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203