Description
Uncontrolled resource consumption in the HTTP/2 (h2) receive path of Apache bRPC (version < 1.18.0) on all platforms allows a remote unauthenticated attacker to crash the server or grow its memory without bound by sending crafted HTTP/2 frames.

Root Cause:
The h2 parser, enabled by default on every bRPC server port and used by h2/gRPC clients, trusts the peer to respect receive-side limits that bRPC advertises but never enforces:
1. SETTINGS_MAX_CONCURRENT_STREAMS defaulted to unlimited and was never checked on the server, letting a peer pin an unbounded number of pending streams per connection (~100x memory amplification).
2. SETTINGS_MAX_HEADER_LIST_SIZE defaulted to unlimited and was never enforced; 1-byte HPACK indexed references amplify a small HEADERS frame ~4000x into an unbounded decoded header list ("HPACK bomb"), and a never-completed HEADERS/CONTINUATION block accumulates memory without limit.
3. Control-frame acks (PING/SETTINGS acks, RST_STREAM, GOAWAY, WINDOW_UPDATE) unconditionally bypassed the -socket_max_unwritten_bytes write cap, so a PING flood combined with withheld TCP reads grew the connection buffer without the documented bound.
4. The HPACK dynamic table size update was validated against the protocol default (4096) instead of the advertised SETTINGS_HEADER_TABLE_SIZE, which together with the dynamic-table queue/accounting issue can desynchronize the decoder and dereference NULL (crash).

Affected scenarios:
Any bRPC server serving HTTP/h2/gRPC to an untrusted network, and any bRPC h2/gRPC client connecting to an untrusted backend. The h2 parser runs before any Authenticator check on the shared port.

How to fix:
Upgrade bRPC, or apply the patch in https://github.com/apache/brpc/pull/3474.

Note:
After applying the fix the following limits are enforced by default:
- max_concurrent_streams: 1024 per connection (4294967295 restores unlimited).
- max_header_list_size: 1 MiB decoded size per stream (4294967295 restores unlimited; -h2_client_max_header_list_size for clients).
- h2 control-frame acks respect -socket_max_unwritten_bytes (-h2_ack_ignore_eovercrowded restores the old behavior).
Requests exceeding these limits are rejected (RST_STREAM(REFUSED_STREAM) or a connection error).
Published: 2026-10-21
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: Uncontrolled resource consumption leading to server crash or memory exhaustion
Action: Immediate Patch
AI Analysis

Impact

Apache bRPC v<1.18.0 has an unbounded resource consumption flaw in the HTTP/2 receive path. The server parses HTTP/2 frames without enforcing advertised limits, allowing a malicious client to send crafted frames that grow the server’s memory unboundedly or trigger a crash. The vulnerability is an uncontrolled resource consumption (CWE-400) and a null pointer dereference (CWE-476). Remote unauthenticated attackers can abuse the flaw by sending large or specially crafted SETTINGS, HEADERS, or control frames, leading to denial of service or memory exhaustion.

Affected Systems

The flaw affects all Apache bRPC deployments that use the HTTP/2 or gRPC interfaces and are running a version older than 1.18.0, on any operating system. Because the HTTP/2 parser is invoked before authentication checks, both servers and clients that connect to untrusted networks are vulnerable.

Risk and Exploitability

Remote and does not require local privileges or prior authentication. Attackers can exploit by sending crafted HTTP/2 frames over an open network connection. EPSS <1% indicates a very low probability of exploitation, and the vulnerability is not in the CISA KEV catalog. However, the lack of enforced limits provides a substantial attack surface for denial of service. The CVSS score of 7.5 indicates high severity given the potential for significant memory growth or crash. Nevertheless, the known exploit conditions combined with the low EPSS suggest the overall risk is notable but exploitation remains unlikely.

Generated by OpenCVE AI on October 30, 2026 at 18:56 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Apache bRPC 1.18.0 or newer, which enforces default limits on concurrent streams, header list sizes, and control frame buffering.
  • If an upgrade is not immediately possible, apply the community patch from https://github.com/apache/brpc/pull/3474 to introduce the missing checks and limits.
  • Restrict access to the bRPC service by placing it behind a firewall or limiting it to trusted networks, and consider applying stricter application-layer rate limits for HTTP/2 traffic.

Generated by OpenCVE AI on October 30, 2026 at 18:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 30 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 30 Oct 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}


Thu, 22 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache brpc
Vendors & Products Apache
Apache brpc

Wed, 21 Oct 2026 12:00:00 +0000

Type Values Removed Values Added
Description Uncontrolled resource consumption in the HTTP/2 (h2) receive path of Apache bRPC (version < 1.18.0) on all platforms allows a remote unauthenticated attacker to crash the server or grow its memory without bound by sending crafted HTTP/2 frames. Root Cause: The h2 parser, enabled by default on every bRPC server port and used by h2/gRPC clients, trusts the peer to respect receive-side limits that bRPC advertises but never enforces: 1. SETTINGS_MAX_CONCURRENT_STREAMS defaulted to unlimited and was never checked on the server, letting a peer pin an unbounded number of pending streams per connection (~100x memory amplification). 2. SETTINGS_MAX_HEADER_LIST_SIZE defaulted to unlimited and was never enforced; 1-byte HPACK indexed references amplify a small HEADERS frame ~4000x into an unbounded decoded header list ("HPACK bomb"), and a never-completed HEADERS/CONTINUATION block accumulates memory without limit. 3. Control-frame acks (PING/SETTINGS acks, RST_STREAM, GOAWAY, WINDOW_UPDATE) unconditionally bypassed the -socket_max_unwritten_bytes write cap, so a PING flood combined with withheld TCP reads grew the connection buffer without the documented bound. 4. The HPACK dynamic table size update was validated against the protocol default (4096) instead of the advertised SETTINGS_HEADER_TABLE_SIZE, which together with the dynamic-table queue/accounting issue can desynchronize the decoder and dereference NULL (crash). Affected scenarios: Any bRPC server serving HTTP/h2/gRPC to an untrusted network, and any bRPC h2/gRPC client connecting to an untrusted backend. The h2 parser runs before any Authenticator check on the shared port. How to fix: Upgrade bRPC, or apply the patch in https://github.com/apache/brpc/pull/3474. Note: After applying the fix the following limits are enforced by default: - max_concurrent_streams: 1024 per connection (4294967295 restores unlimited). - max_header_list_size: 1 MiB decoded size per stream (4294967295 restores unlimited; -h2_client_max_header_list_size for clients). - h2 control-frame acks respect -socket_max_unwritten_bytes (-h2_ack_ignore_eovercrowded restores the old behavior). Requests exceeding these limits are rejected (RST_STREAM(REFUSED_STREAM) or a connection error).
Title Apache bRPC: Unbounded Resource Consumption and Crash in the HTTP/2 Receive Path
Weaknesses CWE-400
CWE-476
References

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-30T16:55:00.165Z

Reserved: 2026-08-22T09:17:53.072Z

Link: CVE-2026-78058

cve-icon Vulnrichment

Updated: 2026-10-30T16:52:24.174Z

cve-icon NVD

Status : Deferred

Published: 2026-10-21T12:17:23.373

Modified: 2026-10-30T17:17:28.880

Link: CVE-2026-78058

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-30T19:00:17Z

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-476

    NULL Pointer Dereference