Apache bRPC (version · Uncontrolled Resource Allocation
Source GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 1.18.0 soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% 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:N/UI:N/S:U/C:N/I:N/A:HExploitation 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
A fix is available in Apache bRPC version 1.18.0, which caps the array item count to the remaining bytes of the array payload to prevent excessive memory allocation. Users should upgrade to version 1.18.0 or apply the patch available at https://github.com/apache/brpc/pull/3451. No additional mitigations are required once the fix is applied.
Description
Apache bRPC versions prior to 1.18.0 contain an uncontrolled resource allocation vulnerability in the mcpack2pb component. This flaw allows remote attackers to cause the server to allocate excessive memory by sending a specially crafted mcpack request with an abnormally large array item count. The vulnerability arises because the mcpack2pb parser trusts the declared item count without validating it against the actual payload size, leading to potential process aborts due to memory exhaustion.