Summary
Go Ethereum vulnerable to DoS via malicious p2p message
Workarounds
Unfortunately, no workaround is available.
Credits
This issue was originally reported to Polygon Security by David Matosse (@iam-ned).
Impact
A vulnerable node can be forced to shutdown/crash using a specially crafted message.
During the peer-to-peer connection handshake, a shared secret key is computed. The implementation
did not verify whether the EC public key provided by the remote party is a valid point on the secp256k1 curve.
By simply sending an all-zero public key, a crash could be induced due to unexpected results from the handshake.
The issue was fixed by adding a curve point validity check in https://github.com/ethereum/go-ethereum/commit/159fb1a1db551c544978dc16a5568a4730b4abf3
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
A fix has been included in geth version 1.14.13 and onwards.
Frequently Asked Questions
- What is CVE-2025-24883? CVE-2025-24883 is a medium-severity improper input validation vulnerability in github.com/ethereum/go-ethereum (go), affecting versions >= 1.14.0, < 1.14.13. It is fixed in 1.14.13. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of github.com/ethereum/go-ethereum are affected by CVE-2025-24883? github.com/ethereum/go-ethereum (go) versions >= 1.14.0, < 1.14.13 is affected.
- Is there a fix for CVE-2025-24883? Yes. CVE-2025-24883 is fixed in 1.14.13. Upgrade to this version or later.
- Is CVE-2025-24883 exploitable, and should I be worried? Whether CVE-2025-24883 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-24883 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-24883? Upgrade
github.com/ethereum/go-ethereumto 1.14.13 or later.