Home » Blockchain » Besu 26.7.1 Fixes Five Denial-of-Service Flaws

Besu 26.7.1 Fixes Five Denial-of-Service Flaws

CertiK found five resource-exhaustion bugs in the Besu Ethereum client. Besu 26.7.1 fixed them on July 27, and advisories followed on August 14.

Abstract digital network security illustration representing the Besu security patch protecting Ethereum nodes

Besu is an open-source Ethereum client written in Java. Banks and enterprises run it on private networks, and it also runs on the public network. On July 27, 2026, the project shipped a security release that fixes five denial-of-service bugs found by the security firm CertiK.

Item Detail
Fixed version Besu 26.7.1 (released July 27, 2026)
Found by CertiK
Advisories Four, published August 14; CertiK’s account followed on August 21
Type of bug Denial of service (unbounded memory or threads)
CVE None assigned
Exploitation None reported

The five bugs

All five let an attacker make a node consume unbounded memory or threads. None involves stolen funds or forged blocks. CertiK’s write-up lists them like this.

Bug Besu severity Fix in 26.7.1 Source
Block hash announcements spawn unbounded threads Major Bounded, fixed-size thread pool CertiK
Future-dated consensus proposals exhaust heap Major Total byte budget with eviction CertiK
Unlimited WebSocket subscriptions grow memory Medium New limit option, –rpc-ws-max-active-subscriptions CertiK
Unknown-parent block announcements share the thread flaw Medium Same thread pool change CertiK
HTTP JSON-RPC filters exhaust memory Minor New limit option, –rpc-max-active-filters (default 1000) CertiK

CertiK says one peer using default P2P access could push a well-provisioned node to tens of thousands of threads and an out-of-memory kill within seconds. Aimed at a majority of validators on a QBFT network, that stalls consensus. In a four-validator test network, the future-proposal bug removed enough validators to halt commit quorum. Private, permissioned chains are therefore the most exposed deployments.

Besu hasn’t said these bugs were exploited, and coverage from Bitcoin.com News, which summarizes the release, reports no active exploitation. But the four advisories ended the quiet period on August 14, so unpatched nodes are now easier to target.

What operators should do

Upgrade to 26.7.1 or newer. Check which interfaces are exposed: P2P, HTTP RPC, WebSocket RPC, and consensus-facing ports. Test in staging first, and coordinate with other validators on a consortium network. Bitcoin.com News also recommends preparing rollback and monitoring steps.

Who Benefits and How

  • Teams running Besu nodes, especially banks and enterprises on private networks, are protected once they upgrade to 26.7.1 or newer. The patch is available now.
  • Customers of those organizations benefit indirectly: a validator that can’t be knocked offline keeps a permissioned chain running.
  • If you don’t run a node, there’s nothing for you to do.

What the reports leave open

No CVE exists for these bugs, and each advisory says so, per Hackernoon’s account of the CertiK research, so scanners that rely on CVE databases won’t flag old Besu versions. The articles don’t list the earliest affected version, so assume anything before 26.7.1 is affected. Severity ratings are Besu’s own, and CertiK’s reading of the impact on QBFT networks is stronger than a public-node view suggests. The “about 7.5% of public execution nodes” figure comes from an Ethernodes count of 8,023 nodes in August 2026, and Hackernoon notes other trackers give 8% to 15% depending on method, so treat the share as a range. Finally, the gap between the July 27 patch and the August 14 advisories was 18 days, per Hackernoon, which means operators who waited for advisories before upgrading had less time than the release implied.

Quick answers

Which Besu version fixes these flaws? Version 26.7.1, released July 27, 2026.

Can these bugs steal funds? Not according to the sources. They are denial-of-service bugs that make nodes slow or crash.

Does this affect Ethereum as a whole? Public Ethereum runs several client programs, so the effect on the full network is limited. Private networks that rely on Besu validators face more risk.

Why is there no CVE number? Besu’s advisories state that no CVE has been assigned. Hackernoon notes this can hinder enterprises that depend on automated vulnerability scanning.

Sources

Related Reading