CVE-2026-79704
Deferred Deferred - Pending Action

Out-of-Bounds Read in Apache bRPC Streaming RPC Client

Vulnerability report for CVE-2026-79704, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-21

Last updated on: 2026-10-30

Assigner: Apache Software Foundation

Description

An out-of-bounds read vulnerability exists in the streaming RPC client of Apache bRPC (versions 1.11.0 throughΒ  1.17.0) on all platforms. A client that creates multiple streams in a single RPC expects the server response to carry exactly one extra_stream_id for every additional stream. The response handling path indexed the returned identifiers using the locally created stream count without first validating the size of the returned list, so a malicious or compromised server (or an on-path attacker) can trigger an out-of-bounds read in the client by returning a malformed StreamSettings response with fewer extra_stream_ids than expected. This may crash the client process (denial of service) or leak unintended memory contents into subsequent stream handling; surplus identifiers have no valid client-stream mapping and are processed inconsistently. Root Cause: Since bRPC 1.11.0, a client can create multiple streams in one RPC via batch StreamCreate. The expected behavior is that the server response must return exactly (N-1) extra_stream_ids, where N is the number of locally created streams. In Controller::HandleStreamConnection, the response path reads extra_stream_ids[i-1] for each additional local stream without first comparing the returned list size with (N-1). If the server returns fewer identifiers, the read runs past the end of the returned list (out-of-bounds read); if it returns more, the surplus identifiers have no corresponding client-side stream. Affected Scenarios: A bRPC client using multi-stream RPC (creating more than one stream in a single RPC) that connects to an untrusted, malicious, or compromised server or to a server reached through an untrusted network path. The server sends a malformed StreamSettings response to trigger the issue. How to Fix: (Choose one of the following options)Β  1. Upgrade bRPC to version 1.18.0, which fixes this issue. 2. Apply this patch: https://github.com/apache/brpc/pull/3485 Note: The fix makes the client reject responses whose extra_stream_ids count does not exactly match the number of additional client streams. Such mismatched responses now fail the RPC with ERESPONSE and go through the existing stream cleanup path, instead of being partially processed.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-21
Last Modified
2026-10-30
Generated
2026-11-10
AI Q&A
2026-10-22
EPSS Evaluated
2026-11-09
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Apache Software Foundation Apache bRPC 1.11.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an out-of-bounds read vulnerability in Apache bRPC's streaming RPC client (versions 1.11.0 to 1.17.0). A client creating multiple streams in one RPC expects the server to return a specific number of extra stream IDs. The client fails to validate the server's response size before accessing these IDs, allowing a malicious server or attacker to send a malformed response. This causes the client to read beyond the allocated memory, potentially crashing the process or leaking sensitive data.

Detection Guidance

This vulnerability can be detected by monitoring for crashes or memory leaks in bRPC clients using multi-stream RPC. Check logs for ERESPONSE errors or segmentation faults. Inspect network traffic for malformed StreamSettings responses with mismatched extra_stream_ids counts.

Impact Analysis

If you use a vulnerable bRPC client with multi-stream RPC and connect to an untrusted server or network, an attacker could exploit this to crash your application (denial of service) or expose memory contents. This is most critical for clients processing sensitive data or operating in high-risk environments.

Compliance Impact

This vulnerability does not directly affect compliance with standards like GDPR or HIPAA. It primarily causes denial of service or memory leaks in bRPC clients using multi-stream RPC with untrusted servers. Compliance impact would only occur if such disruptions led to unauthorized data access or processing failures in regulated environments.

Mitigation Strategies

Upgrade bRPC to version 1.18.0 or apply the patch from https://github.com/apache/brpc/pull/3485. Avoid using multi-stream RPC with untrusted servers or networks until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-79704. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...