Live › vulnerability › CVE-2026-78334
Go to dashboardApache bRPC before 1.18.0 does not run the authentication check on streaming RPC frames, so a remote peer can send streaming frames to a server that is configured with an Authenticator without logging in. A stream can also accept frames from a socket other than the one that created it when the frame carries the stream's id.
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.
Servers built on Apache bRPC that configure an Authenticator and serve streaming RPC are exposed, most of all when they accept traffic from untrusted networks. Deployments without an Authenticator, or without streaming RPC, are not described as affected by the sources.
No product ranges from the sources yet.
grep -rn "BRPC_VERSION\|brpc" CMakeLists.txt or the package manager lock file; versions below 1.18.0 are affected.ServerOptions.auth to an Authenticator and serves streaming RPC (brpc::StreamCreate or StreamAccept).1.18.0.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Missing authentication in the streaming RPC path of Apache bRPC (version < 1.18.0) on all platforms allows a remote attacker to bypass server authentication and inject or deliver streaming frames, when a server is configured with an Authenticator.
Root Cause: When authentication is configured, streaming RPC frames are consumed directly by the streaming parser (ParseStreamingMessage) and never pass through InputMessenger's authentication hook, so an unauthenticated peer can exchange frames without being authenticated. In addition, a server-accepted stream is bound lazily to the first frame that happens to carry its id, so a stream could accept a frame carrying its id from a socket other than the socket that created the stream.
Affected Scenarios: A bRPC server configured with authentication that serves streaming RPC from an untrusted network, or a deployment where a foreign connection can impersonate a stream by id, can be made to accept unauthorized streaming frames.
How to Fix: Upgrade bRPC to 1.18.0, which fixes this issue, or apply the patch in PR https://github.com/apache/brpc/pull/3481.
Note: The fix rejects streaming frames on server sockets when configured authentication has not completed, and keeps server-accepted streams bound to the socket of their creating RPC and rejects frames arriving from another socket. Authenticated streaming RPC behavior and the wire format are unchanged; only unauthenticated or foreign-socket frames are now rejected.
This page as .md · .json · in your agent: get_signal("CVE-2026-78334")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.