CVE-2025-62370VulnerabilityPublished 15 Oct 2025

CVE-2025-62370: alloy-rs core · Uncaught Exception

Affects alloy-rs coreSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.8.26 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.8.26

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade alloy-rs/core to 0.8.26.

Affected software

Product	Affected	Fixed in
crates.ioalloy-rs/core`pkg:cargo/alloy-rs/core`Other threats	Affected <0.8.26	Fixed in 0.8.26

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately identify and inventory all systems using alloy-rs core libraries, focusing on versions prior to 0.8.26 and between 1.0.0 and 1.4.1. The primary mitigation is to upgrade to alloy-rs version 0.8.26 or 1.4.1 and later, where the vulnerability is patched. In environments where immediate patching is not feasible, implement robust input validation and sanitization at the application layer to prevent malformed data from reaching the vulnerable function. Deploy monitoring to detect repeated panics or crashes related to eip712_signing_hash() usage. Utilize external auto-restarting mechanisms cautiously, ensuring they do not mask repeated exploitation attempts. Conduct thorough testing of Ethereum-related services after patching to confirm stability. Additionally, consider network-level protections such as rate limiting and anomaly detection to reduce the risk of automated DoS attempts exploiting this vulnerability. Maintain up-to-date threat intelligence feeds to monitor for any emerging exploits targeting this CVE.

Description

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.

Impact

The primary impact of CVE-2025-62370 is denial-of-service, which can disrupt Ethereum-related services that depend on alloy-rs core libraries. For European organizations, this can affect blockchain infrastructure providers, decentralized finance (DeFi) platforms, cryptocurrency exchanges, and any network services implementing Ethereum smart contract interactions using alloy-rs. Service outages could lead to financial losses, reputational damage, and reduced trust from users and partners. Since the vulnerability does not affect confidentiality or integrity, data breaches or unauthorized modifications are unlikely. However, availability disruptions in critical blockchain services could have cascading effects on transaction processing and smart contract execution. Organizations with high availability requirements may experience significant operational challenges. The lack of required authentication or user interaction means attackers can remotely trigger the DoS, increasing the risk of widespread impact. European financial hubs and technology centers with active Ethereum development and deployment are particularly at risk.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 15:38 UTC

WeaknessesCWE-248

Technical details

References

Community reviews

Related threats