Skip to content

Parallax v2.1.1

Choose a tag to compare

@github-actions github-actions released this 05 Oct 18:44
· 211 commits to main since this release
0951909

Parallax v2.1.1 is a security release. It brings in every applicable security fix published by go-ethereum since the codebase Parallax forked from (geth 1.10.18), along with around 150 upstream crash, DoS, data-race and correctness fixes. All node operators should upgrade, and should rotate their p2p node key afterwards (see Upgrading).

This release does not change consensus rules. v2.1.1 nodes stay on the same chain as earlier releases and interoperate with them.

Security

  • CVE-2026-26315: an invalid-curve flaw in the ECIES implementation used by the RLPx handshake could let a remote peer extract bits of the node's p2p private key. Fixed; rotate your node key after upgrading.
  • CVE-2026-26314: a crafted public key with out-of-range coordinates could crash the node in secp256k1. Fixed.
  • CVE-2026-22862: a correctly authenticated but too-short ECIES message during the handshake crashed the node. Fixed.
  • CVE-2025-24883: handshake public keys are now explicitly checked to be on the secp256k1 curve. Parallax was already protected through the standard-library decoding path; the check is now explicit and covered by tests.
  • CVE-2026-26313: a peer could send unrequested or oversized prl and snap responses that were fully decoded, at many times their wire size in memory, before any check. Responses are now matched against outstanding requests and validated before their contents are decoded. Block bodies are decoded only once their transaction root matches the requested header.
  • CVE-2024-32972: header requests with a zero count could bypass the maximum-headers limit. Releases since v0.1.4 already carried go-ethereum's fix for this CVE, which caps header reads from the freezer at 2 MB, but recent headers not yet moved to the freezer could still be served past the limit, up to several MB per request. Zero-count requests now return an empty response, and requests with an overflowing skip are stopped instead of wrapping around. The zero-count case was reported by Bob Verga (@vergavalle).
  • Snap sync range proofs: a malicious snap peer could inject fabricated account or storage entries in front of the requested range, and they passed proof verification. Fixed.
  • GraphQL (CVE-2023-42319): crafted GraphQL queries could exhaust node resources. Queries are now limited to a nesting depth of 20, a 5 MB request body and a 60 second timeout, and the resolver data races are fixed.
  • RLPx handshake messages are capped at 2 KB.

P2P and sync hardening

  • Transaction pool: the upstream DoS defenses against pool flooding and eviction abuse are in. Separately, the pool's price heap was never rebuilt on chains without London (Parallax mainnet and testnet), so it kept growing with stale entries; it is now rebuilt. Nonces are capped at 2^64 - 1 on admission, and the pending-nonce cache no longer grows without bound from RPC queries for unknown accounts.
  • Peers are dropped for sending transaction messages that contain duplicates, or block bodies and receipts that fail validation. Peers that deliver many invalid transactions are throttled.
  • Snap sync throttles trie-heal requests when peers stall, handles idle-but-busy peers, and no longer fails on empty storage ranges.
  • Downloader: fixed a timeout-resurrection panic, a subtle queue delivery flaw, pivot moves after state commit, and a deadlock when a peer set error occurred.
  • Disconnect reasons are encoded and decoded correctly. Previously every remote disconnect was reported as reason 0.
  • Discovery: ping packets are verified before they are processed, bootnodes outside --netrestrict are filtered out, and a timeout-loop bug and a data race in the dial scheduler are fixed.

RPC

New limits, with upstream defaults:

Flag Default Purpose
--rpc.batch-request-limit 1000 Maximum requests per batch
--rpc.batch-response-max-size 25 MB Maximum bytes returned by a batch
--rpc.http-body-limit 5 MB Maximum HTTP request body
--rpc.logquerylimit 1000 Maximum addresses or topics per position in a log filter
--rpc.rangelimit 0 (off) Maximum block range for log queries

Method names are length-limited, log filters accept at most 4 topic positions, and the WebSocket read limit can now be configured. HTTP servers shut down gracefully, and the server's connection tracking race is fixed.

Fixes

  • Crashes: tracer memory reads (prestate and JS), debug_getRawReceipts and debug_traceTransaction for unknown transactions, querying pending or finalized before they exist, invalid signature lengths, smartcard wallet APDU decryption, keystore keys outside the curve order, ABI event unpacking with empty topics, freezer metadata errors, and a panic when the keystore is unavailable.
  • Overflows: receipt index conversion, gas estimation bounds, and ABI topic encoding for negative or over-wide integers.
  • Data races and deadlocks: tracer interruption, txpool caches, clique, event Resubscribe, log-filter subscriptions, and the bloombits matcher.
  • Freezer durability: index and head files are fsynced in the correct order, read-only mode never mutates files, and file descriptors no longer leak on error paths.
  • Reorgs to a shorter chain now clear stale canonical-hash markers.
  • Log output escapes control and bidirectional-override characters, so remote data can't spoof terminal output.
  • eth_getProof copies the storage trie once per request and accepts at most 1024 keys.
  • xhash: immature coinbase rewards are reported as circulating supply. Temporary files from DAG generation are cleaned up.
  • docker: base packages are upgraded in the deploy stage. golang.org/x/crypto is bumped to v0.55.0.

Behaviour changes

These match current go-ethereum behaviour:

  • Peers that send unsolicited, oversized or late prl or snap responses are disconnected instead of ignored.
  • JSON-RPC requests must carry "jsonrpc": "2.0". null is rejected for required arguments, and an empty {} block parameter is rejected.
  • Transaction-sending calls reject a chainId that doesn't match the node's chain instead of keeping it.
  • A log query with an inverted range, or a fromBlock past the chain head, returns an error instead of [].
  • JWT authentication failures return HTTP 401.

Upgrading

No database migration is needed. After upgrading, rotate the p2p node key, as recommended for CVE-2026-26315:

  1. Stop the node.
  2. Delete <datadir>/Parallax/nodekey.
  3. Start the node. A new key, and so a new node ID and enode URL, is generated.

Update any static or trusted peer lists that reference the old enode.

Full Changelog: v2.1.0...v2.1.1