Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]#29
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
Update module github.com/ethereum/go-ethereum to v1.17.0 [SECURITY]#29renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
1a933ca to
9f68e79
Compare
9f68e79 to
6c45650
Compare
6c45650 to
a817aa1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.14.13→v1.17.0GitHub Vulnerability Alerts
CVE-2026-22862
Impact
A vulnerable node can be forced to shutdown/crash using a specially crafted message.
More details to be released later.
Credit
This issue was reported to the Ethereum Foundation Bug Bounty Program by DELENE TCHIO ROMUALD.
CVE-2026-22868
Impact
An attacker can cause high CPU usage by sending a specially crafted p2p message.
More details to be released later.
Credit
This issue was reported to the Ethereum Foundation Bug Bounty Program by @Yenya030
CVE-2026-26313
Impact
An attacker can cause high memory usage by sending a specially-crafted p2p message.
More details to be released later.
Patches
The issue is resolved in the v1.17.0 release.
Credit
This issue was reported to the Ethereum Foundation Bug Bounty Program by @revofusion
CVE-2026-26314
Impact
A vulnerable node can be forced to shutdown/crash using a specially crafted message.
More details to be released later.
Patches
The problem is resolved in the v1.16.9 and v1.17.0 releases of Geth.
Credit
This issue was reported to the Ethereum Foundation Bug Bounty Program by Waleed Ahmed from vulsight.com
CVE-2026-26315
Impact
Through a flaw in the ECIES cryptography implementation, an attacker may be able to extract bits of the p2p node key.
Patches
The issue is resolved in the v1.16.9 and v1.17.0 releases of Geth. We recommend rotating the node key after applying the upgrade, which can be done by removing the file
<datadir>/geth/nodekeybefore starting Geth.Credit
The issue was reported as a public pull request to go-ethereum by @fengjian.
Release Notes
ethereum/go-ethereum (github.com/ethereum/go-ethereum)
v1.17.0: Eezo-Inlaid Circuitry (v1.17.0)Compare Source
This is a feature release, with all accumulated development from the last 3 months. See below for the highlights.
Note that this release contains multiple critical security fixes, as well as many bug fixes, and is recommended for all users. However, if you are cautious about upgrades, you can also install v1.16.9 which has just the critical security fixes. Specifically, this release fixes CVE-2026-26313, CVE-2026-26314, CVE-2026-26315.
We recommend recreating your p2p node key after installing this update, which you can do by removing the
DATADIR/geth/nodekeyfile before restarting geth. Note this will cause a change in the p2p node ID, which may break static peering setups.Highlights
Path-based Archive Node with Proofs
The path-based archive node can now serve proofs (via
eth_getProof) for the state of older blocks.You can configure the block range that supports proving independently from other archive state availability. Specifically, you can use the
--history.trienodecommand-line flag to set the amount of blocks for which tree nodes will be tracked.This feature is disabled by default. Note that state history cannot easily be recovered once deleted, as it can only be generated by processing blocks. However, you can enable trienode history (and/or state history) at any time to turn a full node into a partial archive node, keeping state from that point in time onwards.
#32727, #32621, #33551, #32981, #33399, #32913, #33303, #33584, #33329, #33681, #33103, #33098, #33515, #32247
EraE History Support
Geth now suports the EraE file format, an archival format for post-merge chain history.
#32157, #33827
OpenTelemetry Tracing
OpenTelemetry tracing is now supported by the RPC server, including support for distributed tracing.
We have also added some tracing spans for block processing via the engine API, i.e.
engine_newPayload.#33599, #33452, #33780, #33521
All Changes
Geth CLI
geth version-checksubcommand has been removed. This command checked the geth website for signed vulnerability notices, and would tell if updates are necessary (#33498)--miner.maxblobscommand-line flag to set a limit on blobs included in built blocks (#33129, #33302)geth --devmode was fixed (#33146)--rpc.rangelimitflag configures the maximum block range foreth_getLogs(#33163)geth --exitwhensyncedwill now set thefinalizedandsafeblock (#33038)geth --ethstatsnow reports the newPayload processing time to the stats server (#33395)evm blocktestcommand can now read filenames from stdin when no path is provided (#32824)Fork Implementation
Core
OnStateUpdatehook, which is called after all state of a block has been committed. This gives access to the changeset of the block. (#33490)setHeadoperation now unsets the finalized block, in cases where the rolled-back block range extends before it. (#33486)SignatureValuesmethod oftypes.Signernow reports an error for invalid signature sizes (#33647)Library
SignTextWithPassphrasenow works correctly with all supported hardware wallets (#33138)bitutil.XORBytesfunction has been deprecated in favor of stdlib package crypto/subtle (#33331)RPC
eth_getTransactionByHashnow returns theblockTimestampas part of the transaction object (#33709)eth_simulateV1,eth_getLogs,eth_getStorageAthave been improved to better comply with the execution RPC spec (#33007, #33320, #33282)eth_simulateV1now selects the correct set of precompiles for the simulated header (#33363)eth_sendTransactionandeth_fillTransactionnow default to EIP-1559 (#33058)gasPriceis now retrievable for transaction types 0x3 and 0x4 (#33542)ethclient(#33693, #33242, #33464)gethclienthas a new wrapper of thecallTracer(#31510)callTracer, reported logs now contain anindexfield which is the index of the log within the transaction (#33629)P2P Networking
setHeadoperations during sync (#33481)5b99d2b)For a full rundown of the changes please consult the Geth 1.17.0 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go(use "stable" tag).v1.16.9: Shield Focusing Module (v1.16.9)Compare Source
This is a security hot-fix release. Specifically, this release fixes CVE-2026-26314, CVE-2026-26315.
We recommend recreating your p2p node key after installing this update, which you can do by removing the
DATADIR/geth/nodekeyfile before restarting geth. Note this will cause a change in the p2p node ID, which may break static peering setups.As with all our previous releases, you can find the:
ethereum/client-go(use "stable" tag).v1.16.8: Moisture Filters (v1.16.8)Compare Source
This is a security fix release and is recommended for all users. It resolves two p2p
vulnerabilities reported through the Ethereum Foundation bug bounty program.
As with all our previous releases, you can find the:
ethereum/client-go(use "stable" tag).v1.16.7: Ballistic Drift Stabilizer (v1.16.7)Compare Source
This is a re-roll of v1.16.6, including an important fix in the KZG cryptography library.
This release enables the Fusaka hardfork on Ethereum mainnet.
The Fusaka fork is scheduled to occur at
2025-12-03 21:49:11 UTC.Please upgrade your node to v1.16.7 in time for the fork.
This release also enables two blob-parameter-only (BPO) upgrades.
These upgrades change protocol parameters to increase the available blob capacity.
2025-12-092026-01-07Fusaka
geth --devmode (#32917)RPC
eth_sendRawTransactionSyncwhich waits until either a timeout or the transaction is mined. This feature is mostly useful on L2s with lower blocktimes. (#32830, #32930, #32929)eth_simulateV1in ethclient (#32856)debug_traceCall(#33015)Core
geth --genesisflag as an alternative to runninggeth init genesis.json(#32844)eth_getProofrequest with the new path-based archive node. (#32907, #32914, #32937)Networking
For a full rundown of the changes please consult the Geth 1.16.6 and 1.16.7 release milestones.
As with all our previous releases, you can find the:
ethereum/client-go(use "stable" tag).v1.16.6: Leather Wrapping (v1.16.6)Compare Source
This release enables the Fusaka hardfork on Ethereum mainnet
The fork is scheduled to occur at
2025-12-03 21:49:11 UTC.This release also enables the BPO1 and BPO2 forks for mainnet at
2025-12-09and2026-01-07respectively.Fusaka
geth --devmode (#32917)RPC
eth_sendRawTransactionSyncwhich waits until either a timeout or the transaction is mined. This feature is mostly useful on L2s with lower blocktimes. (#32830, #32930, #32929)eth_simulateV1in ethclient (#32856)debug_traceCall(#33015)Core
geth --genesisflag as an alternative to runninggeth init genesis.json(#32844)eth_getProofrequest with the new path-based archive node. (#32907, #32914, #32937)Networking
For a full rundown of the changes please consult the Geth 1.16.6 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go.v1.16.5: Coolant Cells (v1.16.5)Compare Source
This is a maintenance release. We are issuing this release mostly to add a conversion path for blob proofs submitted via
eth_sendRawTransaction. See https://blog.ethereum.org/2025/10/15/fusaka-blob-update for more information.RPC
eth_sendRawTransactionhas an upgrade path for blob proofs after the Fusaka fork. Note this is temporary. We will remove support for blob proof conversion during the v1.17.x release cycle, please update RPC client libraries to support cell-level (v1) proofs. (#32849)eth_subscribenow supports atransactionReceiptssubscription. There is also a wrapper in ethclient for this new subscription type. (#32697, #32869)eth_simulateV1was fixed to return the block timestamp in logs, likeeth_getLogsdoes. (#32831)BoundContract.Transferwill now verify that the contract has a payable fallback or receive method. (#32374)keccak256preimagetracer has been added. (#32569)Networking
Core
txpool/valid.metermetric has been corrected. (#32845)For a full rundown of the changes please consult the Geth 1.16.5 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go.v1.16.4: Bioelectric Infusers (v1.16.4)Compare Source
This release enables the Osaka (Fusaka) fork on testnets. We also enable two blob-parameter only (BPO) forks for the testnets.
Holesky
1759308480(2025-10-01 08:48:00 UTC)1759800000(2025-10-07 01:20:00 UTC)1760389824(2025-10-13 21:10:24 UTC)Sepolia
1760427360(2025-10-14 07:36:00 UTC)1761017184(2025-10-21 03:26:24 UTC)1761607008(2025-10-27 23:16:48 UTC)Hoodi
1761677592(2025-10-28 18:53:12 UTC)1762365720(2025-11-05 18:02:00 UTC)1762955544(2025-11-12 13:52:24 UTC)With BPO1 and BPO2, the blob capacity of these networks will increase as follows:
15, target:1021, target:14As of this release, the default block gas limit is set to 60M gas.
This is the recommended limit that we, as client authors, feel comfortable with.
CLI commands
geth snapshotand related commands no longer fail due to not finding the trie journal file. (#32531)geth snapshot dumpandgeth export-preimagesis resolved. (#32650)keeper, to the source tree. (#32543, #32638, #32736)RPC
eth_calland related operations were fixed to not apply the EIP-7825 per-transaction gas limit when executing under Osaka fork rules. (#32641)eth_getLogsand other log filtering operations, it is now possible to configure the number of addresses allowed in the filter using the--rpc.logquerylimitflag. (#32327)--state.size-trackingoption enables collection of precise state size numbers, which can be read using thedebug_stateSizeendpoint. (#32362)debug_executionWitnessanddebug_executionWitnessByHashmethods create a block witness for stateless execution. (#32216)Tracing & ABIGEN
CodeChangeV2hook, with aCodeChangeReasonparameter. (#32525, #32535)OnBalanceChangewas not invoked. (#32526)BoundContractinaccounts/abi/bind/v2now exposes anAddressmethod. (#32559)Core
engine_getBlobshas been updated for improved spec compliance and to deal with the conversion of the blob tx proofs. (#32536, #32538, #32578)engineAPI operations, andeth_config, now support BPO-style forks. (#32589, #32615, #32636, #32579)Networking
Build
v1.16.3: Impact Restrictors (v1.16.3)Compare Source
What's Changed
This is a maintenance release to prepare for the Fusaka release next week. It contains a state history rewrite, fixes for the Osaka devnets, performance improvements, and a few bug fixes.
Fusaka
Core
GetBlockReceiptsalso handles pending blocks #32461db inspect#32506RPC
DoEstimateGas#31795debug_seedHash#32495Others
For a full rundown of the changes please consult the Geth 1.16.3 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go.v1.16.2: Sprouted Seed Vial (v1.16.2)Compare Source
This is a maintenance release that includes implementations of the Fusaka EIPs, along with
several new features, optimizations, and bug fixes. Upgrading to this version is optional,
but feedback from those who do is greatly appreciated.
Fusaka:
Core:
SigHashof SetCodeAuthorization for customized signing. (#32298)RPC:
eth_getLogsrequests that include both block hash and block range. (#31877)debug_traceCall. (#32183)debug_syncto perform a trusted full chain sync. (#32177,#32149)Others:
For a full rundown of the changes please consult the Geth 1.16.2 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go.v1.16.1: Repair Actuals (v1.16.1)Compare Source
This is a patch release, fixing some regressions with v1.16.0.
TryPackmethods that return an error for invalid parameter values. (#31692)geth --vmtrace, enabling the live tracer, did not work due to a bug. (#32107)blockTimestampas returned byeth_getLogsis now hex-encoded. (#32129)eth_getLogsand related endpoints now limit the number of queried addresses to 1000. (#31876)eth_getTransactionReceiptshould be a bit faster. (#32021)geth --devmode related todebug_setHeadis resolved. (#31871)For a full rundown of the changes please consult the Geth 1.16.1 release milestone.
As with all our previous releases, you can find the:
ethereum/client-go.v1.16.0: Terran Rivets (v1.16.0)Compare Source
We are proud to present the v1.16.0 release, introducing path-based archive node and several other improvements to the state database implementation. There is also the usual amount of bug fixes and small improvements.
Archive Node
This release includes a new, experimental implementation of the archive node (
--gcmode=archive). As an archive node, Geth stores all historical states, and can thus retrieve account balances, nonces and storage values at old blocks.In previous versions of Geth, running as an archive node was only possible using the legacy 'hash-based' state storage scheme (
--state.scheme=hash). When syncing mainnet the resulting database would reach sizes larger than 20TB, and it all had to be stored on a high-speed SSD.The new implementation provides the state archive in combination with 'path-based' storage (
--state.scheme=path). Comparing to hash-based storage, there are three basic advantages:--history.stateflag.Notably, there is also one drawback with the new archive
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.