Erigon v3.8.1: security release for Ethereum node operators

Summary

Erigon v3.8.1 (released 2026-10-23) includes security fixes according to its release notes. Ethereum node operators running Erigon should review and upgrade.

Affected

• Erigon (erigontech/erigon) versions before v3.8.1

From the release notes

pcli dump-blobs-snapshots preserves existing and preverified segments by default and no longer overwrites valid blob data with empty entries after blob-count pruning (#25174) — by @awskii, @lystopad ## Security - Peer-traffic resilience. Caplin enforces consensus-spec size limits on gossip and peer responses. Historical block access list requests use a separate serving stream and bounded re-execution, protecting block-body and receipt responses (#25119, #25107) — by @domiwei, @yperbasis ## Caplin archive upgrade notes Gloas historical-state fixes change the builder-history format and reduce archive growth (#25256) — by @domiwei, @0xShadowX. - Nodes that already processed Gloas may rebuild historical states from before the fork. Without PtcWindowEpoch snapshots, post-fork history is processed locally. - Downgrading after writing the new builder-history records is not supported. -

Recommended actions

• Upgrade Erigon to v3.8.1 or later
• Check the release notes for any coordinated upgrade deadline or required configuration change

Source & attribution

This 0xCERT advisory relays the Erigon v3.8.1 release notes: https://github.com/erigontech/erigon/releases/tag/v3.8.1. Refer to the upstream project for the authoritative record and any follow-up security advisories.