{"id":25058,"date":"2026-11-06T07:58:09","date_gmt":"2026-11-06T07:58:09","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/11\/06\/bnb-chain-base-respond-to-reth-security-bug-affecting-evm-networks\/"},"modified":"2026-11-06T07:58:09","modified_gmt":"2026-11-06T07:58:09","slug":"bnb-chain-base-respond-to-reth-security-bug-affecting-evm-networks","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/11\/06\/bnb-chain-base-respond-to-reth-security-bug-affecting-evm-networks\/","title":{"rendered":"BNB Chain, Base respond to Reth security bug affecting EVM networks"},"content":{"rendered":"<p> <br \/>\n<br \/><img decoding=\"async\" src=\"https:\/\/media.crypto.news\/2023\/12\/crypto-news-cybersport-girl-play-computer-games-option02.webp\" \/><\/p>\n<div>\n<p class=\"is-style-lead\">BNB Chain and Base have issued security updates after a bug in the Reth Ethereum execution client raised concerns about incorrect blockchain state calculations across several Ethereum-compatible networks.<\/p>\n<div id=\"cn-block-summary-block_0532fc0bf6f9eecdb42777b28c433077\" class=\"cn-block-summary\">\n<p>\n        <span class=\"tabs__item is-selected\">Summary<\/span>\n    <\/p>\n<div class=\"cn-block-summary__content\">\n<ul class=\"wp-block-list\">\n<li>BNB Chain acknowledged a security risk affecting the Reth execution client but said opBNB does not use op-reth and the impact on BSC-Reth remains limited.<\/li>\n<li>Base confirmed that it identified and resolved the Reth bug after discovering the issue on November 4, with no disruption to network operations or impact on users.<\/li>\n<li>The vulnerability could cause affected nodes to calculate incorrect blockchain state roots, potentially creating problems with network synchronization and state verification.<\/li>\n<li>Base released version 1.5.3 and advised node operators to upgrade, while BNB Chain said its developers were preparing a hotfix and monitoring the situation.<\/li>\n<\/ul><\/div>\n<\/div>\n<p><!-- .cn-block-summary --><\/p>\n<p>In a November 6 <a href=\"https:\/\/x.com\/BNBCHAIN\/status\/2118535732075655489?a=2tMjGFaAj0EkfRgwUFw&amp;s=20\" target=\"_blank\">notice<\/a>, BNB Chain acknowledged the security risk affecting Reth but said its opBNB network does not use op-reth, while the impact on BSC-Reth remains limited.<\/p>\n<figure class=\"wp-block-embed is-type-rich is-provider-x wp-block-embed-x\">\n<div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"twitter-tweet\" data-width=\"550\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">Notice: We are aware of the security risk affecting the Reth client. However, opBNB does not use op-reth, and the impact on BSC-Reth is limited.<\/p>\n<p>The team is actively working on a hotfix and monitoring the situation closely to ensure network security.<\/p>\n<p>No action is required from\u2026<\/p>\n<p>\u2014 BNB Chain (@BNBCHAIN) <a href=\"https:\/\/x.com\/BNBCHAIN\/status\/2118535732075655489?ref_src=twsrc%5Etfw\">November 6, 2026<\/a><\/p><\/blockquote>\n<\/div>\n<\/figure>\n<p>The team said it was preparing a hotfix and closely monitoring the situation to protect network security. Developers and users were told that no action was required at the time of the announcement.<\/p>\n<p>Base, meanwhile, confirmed that it had resolved the issue on November 5, after identifying the vulnerability a day earlier. The Coinbase-backed layer 2 network said its operations were not disrupted and user funds were unaffected.<\/p>\n<p>The problem concerns how certain versions of Reth calculate a blockchain\u2019s state root, a cryptographic value representing the current state of accounts, balances, and smart contract storage.<\/p>\n<p>An incorrect calculation could cause affected nodes to disagree with the network\u2019s actual state, potentially interrupting synchronization or producing unreliable state proofs used by applications.<\/p>\n<h2 class=\"wp-block-heading\"><strong>Base releases patch after confirming blockchain state<\/strong><\/h2>\n<p>According to an <a href=\"https:\/\/base-l2.statuspage.io\/\" target=\"_blank\">official status update<\/a>, Base discovered on November 4 that the Reth bug could cause nodes to calculate an incorrect state root under certain conditions.<\/p>\n<p>Because Base uses Reth as part of its execution infrastructure, its developers applied the mitigation and patched all block-building nodes on the same day.<\/p>\n<p>The team subsequently recalculated the network\u2019s state root and confirmed that it matched the correct value.<\/p>\n<p>    <!-- .cn-block-related-link --><\/p>\n<p>Base explained that its proof system independently verifies every state root, providing another mechanism for detecting inconsistencies in blockchain calculations.<\/p>\n<p>\u201cWe\u2019ve verified the current state root is correct and users were not affected,\u201d the team said.<\/p>\n<p>A software update, <a href=\"https:\/\/github.com\/base\/base\/releases\/tag\/v1.5.3\" target=\"_blank\">version 1.5.3<\/a>, was released to prevent Base validators from halting when encountering invalid state roots.<\/p>\n<p>Node operators were advised to install the update as soon as possible, although Base said they would not need to resynchronize their nodes or perform additional recovery procedures.<\/p>\n<p>The network\u2019s November 5 status notice listed a maintenance window running until November 7 at 16:19 UTC, while the public patch became available at 17:52 UTC on November 5.<\/p>\n<h2 class=\"wp-block-heading\"><strong>Reth developers fix state root calculation bug<\/strong><\/h2>\n<p>The underlying issue originated in Reth, an Ethereum execution client developed by Paradigm that is used directly or through modified versions across several blockchain networks.<\/p>\n<p>A <a href=\"https:\/\/github.com\/paradigmxyz\/reth\/pull\/28264\" target=\"_blank\">GitHub change<\/a> merged on November 3 addressed an error involving how the client\u2019s trie iterator handles certain cached branch boundaries.<\/p>\n<p>The fix changed the iterator\u2019s behavior when searching through stored blockchain data and introduced a regression test covering incremental state root calculations.<\/p>\n<p>Reth developers subsequently included the correction in version 2.10.0, while patched versions of related software included op-reth 2.8.1 and Base\u2019s 1.5.3 release.<\/p>\n<p>Blockchain security firm Blockaid warned that unpatched clients could experience synchronization problems or return incorrect proofs through the eth_getProof interface.<\/p>\n<p>The firm described the problem as a software correctness bug rather than a confirmed exploit and reported no known financial losses associated with the flaw.<\/p>\n<p>The vulnerability prompted responses from networks using Reth-based infrastructure, although their exposure depended on the specific client implementations deployed.<\/p>\n<p>BNB Chain\u2019s announcement distinguished between opBNB, which does not rely on op-reth, and BSC-Reth, where the team acknowledged limited exposure while preparing its own fix.<\/p>\n<h2 class=\"wp-block-heading\"><strong>LayerZero pauses some cross-chain services as precaution<\/strong><\/h2>\n<p>The Reth issue prompted precautionary restrictions beyond the affected execution clients, particularly among services that rely on blockchain state verification.<\/p>\n<p>Cross-chain interoperability provider LayerZero temporarily suspended some off-chain infrastructure connected to affected networks while software fixes were being deployed.<\/p>\n<p>The restrictions delayed certain cross-chain messages, although reports citing the security response said the messages would not be lost.<\/p>\n<p>Some decentralized finance services temporarily restricted deposits or cross-chain routing as operators assessed their exposure.<\/p>\n<p>LayerZero provides interoperability infrastructure used by numerous blockchain applications. In September, <a href=\"https:\/\/crypto.news\/anchorage-digital-taps-layerzero-for-stablecoin-rails~\/\" target=\"_blank\">Anchorage Digital selected LayerZero<\/a> to support cross-chain transfers for stablecoins issued through its federally chartered bank.<\/p>\n<p>The partnership named Tether\u2019s USAT as the first stablecoin to use LayerZero\u2019s Omnichain Fungible Token standard under the arrangement.<\/p>\n<p>Separately, <a href=\"https:\/\/crypto.news\/apechain-chainlink-ccip-ape-usdc-layerzero-migration\/\" target=\"_blank\">ApeChain announced plans<\/a> on November 4 to migrate APE, USDC, and other ecosystem assets from LayerZero to Chainlink\u2019s Cross-Chain Interoperability Protocol.<\/p>\n<p>The migration announcement preceded the public warnings about the Reth vulnerability and concerned ApeChain\u2019s existing cross-chain infrastructure.<\/p>\n<p>For operators running affected Reth-based software, the available updates address the state calculation problem, with Base specifically recommending version 1.5.3 and BNB Chain continuing work on its BSC-Reth hotfix.<\/p>\n<p>    <!-- .cn-block-related-link --><\/p><\/div>\n<p><br \/>\n<br \/><a href=\"https:\/\/crypto.news\/bnb-chain-base-respond-to-reth-security-bug-affecting-evm-networks\/\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>BNB Chain and Base have issued security updates after a bug in the Reth Ethereum execution client raised concerns about incorrect blockchain state calculations across several Ethereum-compatible networks. Summary BNB Chain acknowledged a security risk affecting the Reth execution client but said opBNB does not use op-reth and the impact on BSC-Reth remains limited. Base [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":25059,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tdm_status":"","tdm_grid_status":"","footnotes":""},"categories":[23],"tags":[],"kronos_expire_date":[],"class_list":["post-25058","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-crypto"],"_links":{"self":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/25058","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/comments?post=25058"}],"version-history":[{"count":0,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/25058\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media\/25059"}],"wp:attachment":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media?parent=25058"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/categories?post=25058"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/tags?post=25058"},{"taxonomy":"kronos_expire_date","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/kronos_expire_date?post=25058"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}