Quick answers
- Is CVE-2026-82230 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82230 being exploited in the wild.
- How severe is CVE-2026-82230?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- Apache Brpc < 1.18.0.
- Is there a fix for CVE-2026-82230?
- Yes: fixed in bRPC 1.18.0. Until then: Configure request filtering to reject mcpack messages with nesting depth exceeding 128 levels, or restrict mcpack/ubrpc/public_pbrpc endpoints to trusted networks until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82230 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82230?
- 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
Configure request filtering to reject mcpack messages with nesting depth exceeding 128 levels, or restrict mcpack/ubrpc/public_pbrpc endpoints to trusted networks until upgrading.
Technical details
The mcpack2pb parser in bRPC recursively processes nested objects and arrays without enforcing a depth limit. When a protobuf message contains self-referential or repeated fields, an attacker can send specially crafted mcpack data with extreme nesting depth to exhaust the stack and crash the process. The vulnerability affects servers using recursive-schema protobuf messages to handle nshead_mcpack, ubrpc, or public_pbrpc requests from untrusted networks.
Affected products
- Apache bRPC < 1.18.0
Timeline
- 2026-10-21: disclosed