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