Live › vulnerability › CVE-2026-80463
Go to dashboardApache bRPC before 1.18.0 buffers continuation frames of a fragmented stream message without any size limit. A remote peer that can open a stream can send an endless sequence of these frames and drive the server out of memory, crashing it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Services built on Apache bRPC below 1.18.0 that accept streams from untrusted clients through the built-in streaming protocol are exposed, since the flaw is in how the receiver accumulates fragmented stream messages. Services that only use bRPC with trusted peers, or that do not accept streams from outside, are less exposed and can plan the upgrade on a normal schedule.
No product ranges from the sources yet.
grep -r BRPC_VERSION in the build tree or the package manager's version of the bRPC library; affected if below 1.18.0.brpc::StreamAccept or brpc::StreamCreate over the built-in streaming protocol and accept connections from untrusted clients.1.18.0 or later.max_body_size (default 64MB) are rejected with EMSGSIZE; raise the gflag max_body_size if legitimate messages are larger.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Unbounded memory accumulation in the stream message reassembly path of Apache bRPC (version < 1.18.0) on all platforms allows remote attackers to exhaust the memory of a server (denial of service) by sending an endless sequence of continuation data frames.
Root Cause: The streaming RPC protocol bounds every single data frame by max_body_size, but a fragmented stream message accumulates continuation frames into one buffer (_pending_buf) without any limit on the accumulated size. A malicious peer that can open a stream can therefore keep sending continuation frames to make the receiver accumulate an arbitrarily large in-memory message. Since the default flow-control settings (socket_max_streams_unconsumed_bytes=0) do not throttle the sending rate, the receiver's memory grows until the process runs out of memory and crashes or becomes unavailable.
Affected Scenarios: Services that accept streams from untrusted clients (for example using brpc::StreamAccept or brpc::StreamCreate with the built-in streaming protocol) are affected.
How to Fix: (Choose one of the following options)
Note: The fix limits the accumulated payload of a fragmented stream message to max_body_size (default 64MB). When the accumulated payload exceeds the limit, the pending fragments are released and the stream is closed with error EMSGSIZE. After applying the fix, legitimate fragmented stream messages larger than max_body_size will be rejected; you can adjust the gflag max_body_size to change the limit.
This page as .md · .json · in your agent: get_signal("CVE-2026-80463")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.