Service crash via empty type linearization
Published Oct 15, 2025 · Updated Oct 15, 2025
Denial of service in Alloy Core before 0.8.26 and 1.0.0 through 1.4.0 allows remote attackers to crash consuming services. Resolver::encode_type accepts a TypedData primary type that linearizes to an empty list, then unwraps its absent first element during eip712_signing_hash, causing a panic. Exposure requires an application to pass attacker-controlled EIP-712 typed data into the library; repeated requests can interrupt a network service.
Summary
What happened
Denial of service in Alloy Core before 0.8.26 and 1.0.0 through 1.4.0 allows remote attackers to crash consuming services. Resolver::encode_type accepts a TypedData primary type that linearizes to an empty list, then unwraps its absent first element during eip712_signing_hash, causing a panic. Exposure requires an application to pass attacker-controlled EIP-712 typed data into the library; repeated requests can interrupt a network service.
The record
- CVE
- CVE-2025-62370
- Published
- Oct 15, 2025
- Updated
- Oct 15, 2025
- Vendor
- Alloy
- Product
- Alloy Core
- Classifications
- CWE-248, CWE-20, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 15, 2025CVE publishedPublication date reported by the CVE source.
- Oct 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.8.26
- Affected versionversion=>= 1.0.0, < 1.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo