# CVE-2026-78058: Apache bRPC HTTP/2 receive path resource consumption

Source: https://junglewise.ai/threats/cve-2026-78058-uncontrolled-resource-consumption-in-the-http-2-h2-receive-path  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-21. Updated: 2026-10-21  
License: CC BY 4.0 with a link back

CVE-2026-78058 · Severity: info · Published 2026-10-21

Apache bRPC is a high-performance RPC framework used to build distributed services. A remote attacker can send specially crafted HTTP/2 frames to crash a bRPC server or exhaust its memory without authentication, affecting any server exposed to untrusted networks. The vulnerability exists in the default HTTP/2 parser that runs before security checks.

Technologies: [Apache Brpc](https://junglewise.ai/threats/technologies/brpc). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-78058 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-78058 being exploited in the wild.

**How severe is CVE-2026-78058?** Informational severity, published 21 October 2026.

**Which products and versions are affected?** Apache Brpc < 1.18.0.

**Is there a fix for CVE-2026-78058?** Yes: fixed in bRPC 1.18.0. Until then: Restrict network access to bRPC servers until patched, or use a reverse proxy to validate and enforce HTTP/2 framing limits before traffic reaches bRPC. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-78058 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-78058?** Check whether you run Apache Brpc at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in bRPC 1.18.0

Restrict network access to bRPC servers until patched, or use a reverse proxy to validate and enforce HTTP/2 framing limits before traffic reaches bRPC.

## Technical details

The HTTP/2 parser in bRPC fails to enforce receive-side limits it advertises via SETTINGS frames, including unbounded concurrent streams, unlimited header list size, and improper HPACK dynamic table validation. An attacker can exploit this through multiple vectors: pinning unlimited streams per connection, sending HPACK-compressed headers that amplify to gigabytes of memory, delaying CONTINUATION frames to accumulate state, or flooding PING/SETTINGS acknowledgments that bypass the write buffer cap. The fix enforces strict defaults (1024 concurrent streams, 1 MiB header list size) and respects the socket write buffer limit.

## Affected products

- Apache bRPC < 1.18.0

## Timeline

- 2026-10-21: disclosed

## Related threats

- [Apache bRPC MySQL client null pointer dereference](https://junglewise.ai/threats/cve-2026-90484-the-mysql-client-response-parser-in-apache-brpc-dereferences-a)
- [Apache bRPC Discovery naming-service JSON parsing crash](https://junglewise.ai/threats/cve-2026-87849-the-discovery-naming-service-reply-parser-in-apache-brpc-versions)
- [brpc Server authentication bypass via internal_port](https://junglewise.ai/threats/cve-2026-86249-on-a-brpc-server-that-sets-both-serveroptions-auth-and)
- [Apache bRPC path traversal and resource exhaustion in builtin services](https://junglewise.ai/threats/cve-2026-86147-external-control-of-file-name-or-path-and-uncontrolled-resource)
- [Apache bRPC HTTP request/response smuggling in bundled parser](https://junglewise.ai/threats/cve-2026-86146-inconsistent-interpretation-of-http-requests-http-request)