Skip to content
fr Sign in
Not rated

CVE-2026-61902 Apache bRPC versions before 1.18.0 do not consistently enforce the configured max_body_size limit in non-progressive…

Description

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.

Affected products and versions

Product Affected versions Fixed in
Apache bRPC 1.18 earliest → < 1.18.0 1.18.0

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Apache bRPC

The 41 CVEs of Apache bRPC →
CVE-2026-90484 The MySQL client response parser in Apache bRPC dereferences a null pointer when the server peer sends a… Not rated CVE-2026-87849 The Discovery naming-service reply parser in Apache bRPC (versions < 1.18.0) calls RapidJSON object-only accessors… Not rated CVE-2026-86249 On a brpc::Server that sets both ServerOptions.auth and ServerOptions.internal_port, the HTTP built-in service exemption… Not rated CVE-2026-86147 External control of file name or path and uncontrolled resource consumption in Apache bRPC (version < 1.18.0) on all… Not rated
Track this CVE