VulnerabilityPublished 21 Oct 2026

CVE-2026-82942: Apache bRPC · Race Condition

Affects Apache bRPCSource CVE Database V5

Not known to be exploited : upgrade to 1.18.0 soon.

Data as of 26 Oct 2026, 17:30 UTC

Severity

High

Rated High by the CNA (apache) · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.18.0

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache bRPC and apache/brpc to 1.18.0.

Affected software

Product	Affected	Fixed in
Apache bRPCapache/brpc	Affected <1.18.0	Fixed in 1.18.0
GitHubapache/brpc`pkg:github/apache/brpc`Other threats	Affected <1.18.0	Fixed in 1.18.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache bRPC to version 1.18.0, which contains an official fix for this vulnerability. Alternatively, apply the patch available at https://github.com/apache/brpc/pull/3505. Deployments not using RDMA support are not affected and require no action.

Description

A race condition vulnerability (CWE-362) exists in Apache bRPC versions prior to 1.18.0 when RDMA support is enabled. This flaw allows a remote unauthenticated client to cause a denial of service by crashing the server process due to improper synchronization of shared input buffers during RDMA handshake and message processing. The issue occurs only if the server is built and run with RDMA enabled and accepts connections from untrusted clients. Upgrading to version 1.18.0 or applying the provided patch mitigates the vulnerability.

Impact

A remote, unauthenticated client can exploit this race condition to crash the Apache bRPC server process, resulting in a denial of service. This impacts availability of the affected server. No other impacts such as code execution or data disclosure are described.

Summary

Apache bRPC versions before 1.18.0 contain a data race in the RDMA transport implementation. When RDMA is enabled, the server's TCP file descriptor input stream and RDMA queue pair input stream share parsing buffers and state without proper synchronization. This allows concurrent processing of handshake and RDMA messages to corrupt shared buffers, leading to a server crash. The vulnerability affects deployments using RDMA-enabled bRPC servers that accept connections from untrusted clients. The issue is fixed in version 1.18.0 and a patch is available.

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Architecture and Design
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design
Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design
Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Oct 2026, 12:49 UTC

WeaknessesCWE-362

Technical details

References

Community reviews

Related threats