{"id":"CVE-2026-61902","title":"Apache bRPC: Memory Exhaustion Through Inconsistent Message Body Limits","summary":"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.\n\nA remote unauthenticated peer can cause an af…","severity":"none","cwe":["CWE-400"],"vendor":"Apache Software Foundation","product":"apache/brpc","affected":["apache/brpc < 1.18.0"],"published":"2026-10-21","updated":"2026-10-21","sourceUpdated":"2026-10-21T11:41:56.277Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-61902","references":[{"url":"https://lists.apache.org/thread/2pf15ojj0vr7rtx95677kgtl1mx3gdgb"}],"tags":["cve.org"],"ingestedAt":"2026-10-21T12:48:53.763Z","slug":"CVE-2026-61902","body":"## Overview\n\nApache 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.\n\nA 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. \nUsers 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.\n\n## Affected\n\n- `apache/brpc < 1.18.0`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}