Apache bRPC (versions · Discovery Naming-service Reply Parser
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.18.0 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.18.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation 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.
What to do
Upgrade Apache bRPC and apache/brpc to 1.18.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache bRPCapache/brpc | Affected
| Fixed in
|
GitHubapache/brpcpkg:github/apache/brpcOther threats | Affected
| Fixed in
|
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 or later, which includes the fix validating JSON object types before member access. Alternatively, apply the patch available at https://github.com/apache/brpc/pull/3533. No other mitigation is required as the fix prevents out-of-bounds reads and client crashes.
Description
Apache bRPC versions prior to 1.18.0 contain a vulnerability in the Discovery naming-service reply parser. The parser improperly calls RapidJSON object-only accessors on JSON values without verifying they are objects, leading to out-of-bounds memory reads and potential client crashes when processing malformed Discovery responses. This can occur if the Discovery backend returns non-object entries in data/service members or instance lists. The issue is fixed in version 1.18.0 by validating JSON types before access.