Apache bRPC: Memory Exhaustion Through Inconsistent Message Body Limits
Apache bRPC versions before 1.18.0 do not consistently enforce the configured max_body_size limit in non-progressive HTTP/1 and HTTP/2 parsing and in memcache and couchbase response parsing. A remote unauthenticated peer can cause an affected process to buffer message data beyond the configured limit, which may lead to memory exhaustion and denial of service. Users should upgrade to 1.18.0 or apply the patch from PR https://github.com/apache/brpc/pull/3382 . The fix rejects oversized buffered HTTP bodies, returns HTTP 413 for HTTP/1 requests, resets oversized HTTP/2 streams, and rejects oversized memcache and couchbase responses from their declared lengths. Progressive HTTP reading remains supported because it uses bounded buffering.
CVE-2026-61902
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-61902
Apache bRPC
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "Apache Software Foundation",
"product": "Apache bRPC",
"versions": [
{
"status": "affected",
"version": "0",
"lessThan": "1.18.0",
"versionType": "semver"
}
],
"packageURL": "pkg:github/apache/brpc",
"packageName": "apache/brpc",
"collectionURL": "https://github.com",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-61902
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #45854 · Revision 1
- Added to Heist Feed
- Publisher date