CVE-2026-78058
Deferred Deferred - Pending Action

BaseFortify

Vulnerability report for CVE-2026-78058, 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

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).

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 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-476 The product dereferences a pointer that it expects to be valid but is NULL.
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an uncontrolled resource consumption issue in Apache bRPC's HTTP/2 (h2) receive path affecting versions before 1.18.0. A remote attacker can crash the server or cause unbounded memory growth by sending specially crafted HTTP/2 frames. The h2 parser, enabled by default, fails to enforce advertised limits, allowing attacks like an HPACK bomb or PING flood.

Detection Guidance

Detecting this vulnerability requires monitoring for abnormal memory usage or crashes in Apache bRPC servers using HTTP/2. Check for processes consuming excessive memory or frequent crashes. Use tools like 'top', 'htop', or 'ps' to monitor bRPC server processes. Inspect logs for HTTP/2-related errors or connection drops. Ensure bRPC is updated to version 1.18.0 or later to mitigate the issue.

Impact Analysis

If you run a bRPC server exposed to untrusted networks or connect to untrusted HTTP/2/gRPC backends, an attacker could crash your service or consume excessive server memory, leading to denial of service. The vulnerability affects both servers and clients using HTTP/2.

Compliance Impact

This vulnerability could lead to denial-of-service (DoS) conditions by consuming excessive server resources, potentially disrupting services handling sensitive data. For GDPR, this may impact availability of personal data processing systems. For HIPAA, it could affect the integrity and availability of protected health information systems.

Mitigation Strategies

Upgrade Apache bRPC to version 1.18.0 or later. Alternatively, apply the patch from https://github.com/apache/brpc/pull/3474. After applying the fix, the vulnerability is mitigated by default limits on concurrent streams, header size, and control-frame acks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-78058. 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...