https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 22:39:56 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-212776 EUVD-2026-212776 https://cve.radiocsirt.org/vuln/euvd-2026-212776 https://cve.radiocsirt.org/vuln/fkie_cve-2025-24883 <p>go-ethereum (geth) is a golang execution layer implementation of the Ethereum protocol. A vulnerable node can be forced to shutdown/crash using a specially crafted message. This vulnerability is fixed in 1.14.13.</p> <p>go-ethereum (geth) is a golang execution layer implementation of the Ethereum protocol. A vulnerable node can be forced to shutdown/crash using a specially crafted message. This vulnerability is fixed in 1.14.13.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-24883 https://cve.radiocsirt.org/vuln/ghsa-q26p-9cq4-7fc2 <p><strong>Affected:</strong> Go: github.com/ethereum/go-ethereum</p> <p>### Impact</p> <p>A vulnerable node can be forced to shutdown/crash using a specially crafted message.</p> <p>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.</p> <p>The issue was fixed by adding a curve point validity check in https://github.com/ethereum/go-ethereum/commit/159fb1a1db551c544978dc16a5568a4730b4abf3</p> <p>### Patches</p> <p>A fix has been included in geth version 1.14.13 and onwards.</p> <p>### Workarounds</p> <p>Unfortunately, no workaround is available.</p> <p>### Credits</p> <p>This issue was originally reported to Polygon Security by David Matosse (@iam-ned).</p> <p><strong>Affected:</strong> Go: github.com/ethereum/go-ethereum</p> <p>### Impact</p> <p>A vulnerable node can be forced to shutdown/crash using a specially crafted message.</p> <p>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.</p> <p>The issue was fixed by adding a curve point validity check in https://github.com/ethereum/go-ethereum/commit/159fb1a1db551c544978dc16a5568a4730b4abf3</p> <p>### Patches</p> <p>A fix has been included in geth version 1.14.13 and onwards.</p> <p>### Workarounds</p> <p>Unfortunately, no workaround is available.</p> <p>### Credits</p> <p>This issue was originally reported to Polygon Security by David Matosse (@iam-ned).</p> https://cve.radiocsirt.org/vuln/ghsa-q26p-9cq4-7fc2 https://cve.radiocsirt.org/vuln/opensuse-su-2025:14732-1 <p>govulncheck-vulndb-0.0.20250204T220613-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20250204T220613-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:14732-1 https://cve.radiocsirt.org/vuln/suse-su-2025:0429-1 <p>Security update for govulncheck-vulndb</p> <p>Security update for govulncheck-vulndb</p> https://cve.radiocsirt.org/vuln/suse-su-2025:0429-1