Quick answers
- Is CVE-2026-78334 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78334 being exploited in the wild.
- How severe is CVE-2026-78334?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- Apache Brpc < 1.18.0.
- Is there a fix for CVE-2026-78334?
- Yes: fixed in bRPC 1.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78334 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-78334?
- 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
Technical details
Streaming RPC frames bypass the InputMessenger authentication hook and are consumed directly by ParseStreamingMessage, allowing unauthenticated peers to exchange frames. Additionally, server-accepted streams are bound lazily to the first frame carrying their ID, enabling foreign connections to impersonate streams. The fix rejects streaming frames when authentication has not completed and binds streams to their originating socket.
Affected products
- Apache bRPC < 1.18.0
Timeline
- 2026-10-21: disclosed