What is CVE-2025-53359?

CVE-2025-53359 is a medium-severity security vulnerability in ethereum (rust), affecting versions < 0.18.0. It is fixed in 0.18.0.

Which versions of ethereum are affected by CVE-2025-53359?

ethereum (rust) versions < 0.18.0 is affected.

Is there a fix for CVE-2025-53359?

Yes. CVE-2025-53359 is fixed in 0.18.0. Upgrade to this version or later.

Is CVE-2025-53359 exploitable, and should I be worried?

Whether CVE-2025-53359 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-53359 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-53359 in ethereum

Q: Which versions of ethereum are affected by CVE-2025-53359?

ethereum (rust) versions < 0.18.0 is affected.

Q: Is there a fix for CVE-2025-53359?

Yes. CVE-2025-53359 is fixed in 0.18.0. Upgrade to this version or later.

Q: Is CVE-2025-53359 exploitable, and should I be worried?

Whether CVE-2025-53359 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-53359 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-53359?

Upgrade ethereum to 0.18.0 or later.

Summary

ethereum does not check transaction malleability for EIP-2930, EIP-1559 and EIP-7702 transactions

The issue is fixed in `ethereum` v0.18.0

Workarounds

You can also manually check transaction malleability outside of the crate. But it's recommended to simply upgrade the version.

References

See PR: https://github.com/rust-ethereum/ethereum/pull/67

Impact

Prior to ethereum crate v0.18.0, signature malleability (according to EIP-2) was only checked for "legacy" transactions, but not for EIP-2930, EIP-1559 and EIP-7702 transactions.

This is a specification deviation and therefore a high severity advisory if the ethereum crate is used for Ethereum mainnet. Note that signature malleability itself is not a security issue, and therefore if the ethereum crate is used on a single-implementation blockchain, it's a low/informational severity advisory.

Affected versions

ethereum (< 0.18.0)

Security releases

ethereum → 0.18.0 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade ethereum to 0.18.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-53359? CVE-2025-53359 is a medium-severity security vulnerability in ethereum (rust), affecting versions < 0.18.0. It is fixed in 0.18.0.
Which versions of ethereum are affected by CVE-2025-53359? ethereum (rust) versions < 0.18.0 is affected.
Is there a fix for CVE-2025-53359? Yes. CVE-2025-53359 is fixed in 0.18.0. Upgrade to this version or later.
Is CVE-2025-53359 exploitable, and should I be worried? Whether CVE-2025-53359 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-53359 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-53359? Upgrade ethereum to 0.18.0 or later.