Is CVE-2026-82231 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-82231 being exploited in the wild.

How severe is CVE-2026-82231?

Informational severity, published 21 October 2026.

Which products and versions are affected?

Apache Brpc < 1.18.0 (with WITH_THRIFT build flag enabled).

Is there a fix for CVE-2026-82231?

Yes: fixed in 1.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-82231 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-82231?

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.

CVE-2026-82231: Apache bRPC Thrift client denial of service

Q: Which products and versions are affected?

Apache Brpc < 1.18.0 (with WITH_THRIFT build flag enabled).

Q: Is there a fix for CVE-2026-82231?

Yes: fixed in 1.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-82231 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-82231?

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.

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

Apache bRPC is an open-source remote procedure call (RPC) framework used for service-to-service communication. When built with Thrift support (off by default), a malicious or compromised server can send malformed responses that crash the entire bRPC client process, disrupting all in-flight communication and causing denial of service. This affects deployments that enable the optional Thrift support.

Technologies: Apache Brpc. Vendors: Apache.

Quick answers

Is CVE-2026-82231 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-82231 being exploited in the wild.
How severe is CVE-2026-82231?: Informational severity, published 21 October 2026.
Which products and versions are affected?: Apache Brpc < 1.18.0 (with WITH_THRIFT build flag enabled).
Is there a fix for CVE-2026-82231?: Yes: fixed in 1.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-82231 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-82231?: 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: 1.18.0

Technical details

A Thrift client in Apache bRPC versions below 1.18.0 fails to catch exceptions (TProtocolException, TTransportException, or std::length_error) thrown by Apache Thrift when decoding a malformed T_EXCEPTION reply from the server peer. The unhandled exception unwinds out of the bthread task function, invoking std::terminate() and crashing the entire process. The vulnerability requires WITH_THRIFT build flag enabled and the adversary is the untrusted server peer.

Affected products

Apache bRPC < 1.18.0 (with WITH_THRIFT build flag enabled)

Timeline

2026-10-21: advisory
2026-10-21: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.