---
id: "CVE-2026-61902"
kind: "vulnerability"
aliases: ["CVE-2026-61902"]
title: "Apache bRPC: body size limit not enforced, enabling memory exhaustion denial of service"
severity: "unknown"
cvss: null
epss: 0.00158
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["c++", "memory-exhaustion", "package", "rpc", "self-hosted"]
not_affected_if: ["no-network-exposure", "version-1.18.0-or-later"]
published_at: "2026-10-21T12:17:22+00:00"
first_seen_at: "2026-10-23T21:57:28+00:00"
updated_at: "2026-10-25T05:02:44+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-61902", "first_seen_at": "2026-10-23T21:57:28+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-61902", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# Apache bRPC: body size limit not enforced, enabling memory exhaustion denial of service

Apache bRPC before 1.18.0 does not consistently enforce the configured max_body_size limit when parsing non-progressive HTTP/1 and HTTP/2 requests and memcache and couchbase responses. A remote unauthenticated peer can make the process buffer data beyond that limit, exhausting memory and causing a denial of service.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the bRPC version in use; affected versions are those before `1.18.0`.
- Look for `max_body_size` in the server configuration and for non-progressive HTTP reading or memcache/couchbase client use.

## Fix

- Upgrade bRPC to `1.18.0` or later.
- Alternatively, apply the patch from https://github.com/apache/brpc/pull/3382.

## Timeline

- 2026-10-23T21:57:28+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-61902
- 2026-10-24T13:15:54+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-61902

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_