Reth Releases Version 2.10.0 Hardening Execution Client and SDK
The high-priority release fixes engine thread panics after chain reorganizations and patches file deletion vulnerabilities.
At a glance
- What happened
- Reth released client version 2.10.0 on Nov. 5, 2026, delivering high-priority bug fixes for engine panics and data security.
- Why it matters
- The release stops node crashes during deep chain reorganizations and protects local file systems from directory escape during downloads.
- Who is affected
- Ethereum payload builders, infrastructure providers, and node operators running Reth.
- Takes effect
- 2026-11-05
- What's next
- Node operators and payload builders must upgrade to v2.10.0 or maintain compatibility with v2.9.0.
- Primary source
- Reth releases: Reth v2.10.0
Key points
- Reth v2.10.0 designates an update priority of High for both payload builders and non-payload builders.
- The release fixes an engine-thread panic triggered by chain reorganizations below the persisted tip.
- A breaking SDK change delivers evm2 state changes directly to the commit-condition callback for payload builders.
Ethereum execution client Reth launched version 2.10.0 on Nov. 5, 2026, delivering an infrastructure hardening update marked as high priority for both payload builders and standard node operators 1. The update resolves an engine-thread panic that occurred when constructing an invalid-block witness following a chain reorganization below the persisted tip 1. It also patches a vulnerability in the reth download CLI command, preventing it from deleting files located outside the designated data directory or traversing through symlinked parent directories 1.
Beyond stability fixes, the release introduces a breaking change for developers utilizing the Reth software development kit 1. The commit-condition callback on BlockExecutor and BlockBuilder now receives transaction state changes through evm2::TxStateChanges, allowing builders to filter transactions based on state modifications alongside execution results 1. The release remains backwards-compatible, permitting node operators to downgrade to version 2.9.0 if necessary 1. Operators can trace this release cadence back through previous milestones, such as version 2.8.0 and version 2.7.0.
Performance Gains and RPC Tightening
Version 2.10.0 improves database maintenance workflows by parallelizing the db repair-trie command, which now checks storage across multiple parallel threads using configurable worker and lookahead flags 1. Running this command as a dry run now requires the Reth node to be stopped 1. Tracing capabilities were also broadened with the --tracing-otlp flag, which now supports writing OpenTelemetry spans directly to local file paths without deploying a dedicated external collector 1.
Several RPC endpoints received behavioral constraints to curb resource exhaustion 1. The eth_callBundle method now requires a blocking-IO permit, automatically halts execution if the calling client disconnects, and enforces a single shared gas limit across the entire bundle 1. Pending block construction tasks will similarly abort when incoming requests are canceled 1. Peer-to-peer networking updates ensure that nodes ignore superfluous fields in network handshake messages and retain trusted peer identifiers even if initial domain name system lookups fail 1. At the time of writing, $ETH traded down 6.4% over 24 hours at $2,275.
Sources
- [1] Reth v2.10.0 — Reth releases, November 5, 2026
Written by Basis Desk's newsroom system from the primary sources above and machine-verified against them before publication. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.
The Daily Brief, in your inbox at 07:00 ET
Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.
Get the big crypto stories first
A few alerts a day at most: major breaking news and the morning brief. Switch off anytime.
Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.