Quick answers
- Is CVE-2026-82425 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82425 being exploited in the wild.
- How severe is CVE-2026-82425?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- Apache Brpc versions before 1.18.0.
- Is there a fix for CVE-2026-82425?
- Yes: fixed in bRPC 1.18.0. Until then: Disable health checking by not setting the -health_check_interval flag, or restrict client connections to trusted peers only, until upgrading to version 1.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82425 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82425?
- 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
Disable health checking by not setting the -health_check_interval flag, or restrict client connections to trusted peers only, until upgrading to version 1.18.0.
Technical details
A race condition exists between Socket teardown (closing file descriptor to -1) and health check revival in bRPC versions before 1.18.0. When health checks succeed on a Socket whose fd is still -1, a stale input event (EPOLLIN/EVFILT_READ) triggers a CHECK assertion that crashes the process. The vulnerability requires a malicious remote peer and health check to be explicitly enabled (via -health_check_interval flag), and can be reliably triggered by coordinating connection aborts with health check probes.
Affected products
- Apache bRPC versions before 1.18.0
Timeline
- 2026-10-21: disclosed