Skip to main content
Vulnerability Database/CVE-2026-61902

CVE-2026-61902: Apache bRPC Memory Exhaustion DoS Vulnerability

CVE-2026-61902 is a denial of service vulnerability in Apache bRPC that allows remote attackers to cause memory exhaustion by bypassing message size limits. This article covers technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-61902 Overview

CVE-2026-61902 is a resource exhaustion vulnerability in Apache bRPC versions before 1.18.0. The framework fails to consistently enforce the configured max_body_size limit across several parsing paths. Affected code paths include non-progressive HTTP/1 and HTTP/2 parsing, along with memcache and couchbase response parsing.

A remote, unauthenticated peer can send crafted messages that cause an affected process to buffer data beyond the configured limit. The condition can lead to memory exhaustion and denial of service against bRPC-based services. The weakness is tracked as [CWE-400: Uncontrolled Resource Consumption].

Critical Impact

Unauthenticated remote attackers can exhaust process memory on bRPC services, producing denial of service without any credentials.

Affected Products

  • Apache bRPC versions prior to 1.18.0
  • bRPC services exposing non-progressive HTTP/1 or HTTP/2 endpoints
  • bRPC clients or servers parsing memcache and couchbase responses

Discovery Timeline

  • 2026-10-21 - CVE-2026-61902 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-61902

Vulnerability Analysis

Apache bRPC exposes a max_body_size configuration option intended to cap the size of inbound message bodies. The vulnerability stems from inconsistent enforcement of this limit across multiple parsing code paths. Non-progressive HTTP/1 and HTTP/2 parsers accept and buffer body data without checking the configured ceiling. The memcache and couchbase response parsers similarly fail to validate declared payload lengths before buffering.

An attacker who can reach an affected endpoint can submit requests or responses whose body sizes exceed the configured limit. The server allocates memory to buffer the oversized payloads, leading to memory pressure and eventual process termination. The vulnerability is categorized as a denial of service issue under [CWE-400].

Root Cause

The fix in PR #3382 confirms that the parsers accumulated body bytes without checking the running total against max_body_size. Progressive HTTP reading was not affected because it uses bounded buffering by design.

Attack Vector

A remote unauthenticated peer sends HTTP/1, HTTP/2, memcache, or couchbase traffic with a body larger than max_body_size. The affected parser continues to buffer the data in memory until the process is starved of resources. No authentication is required, and a single peer can repeat the request to accelerate exhaustion.

See the Apache mailing list discussion for upstream coordination details.

Detection Methods for CVE-2026-61902

Indicators of Compromise

  • Rapid growth in resident memory of bRPC server processes without a matching increase in legitimate request volume
  • bRPC processes terminated by the kernel out-of-memory killer
  • Long-lived HTTP/1 or HTTP/2 connections transmitting bodies that exceed the service's documented size limits
  • Memcache or couchbase responses whose declared content length is abnormally large

Detection Strategies

  • Inventory services that embed Apache bRPC and identify any build pinned below version 1.18.0
  • Instrument bRPC services to log request body sizes and alert when a single connection buffers data above max_body_size
  • Correlate process memory metrics with inbound connection counts to identify low-volume, high-memory anomalies consistent with amplification

Monitoring Recommendations

  • Track per-process RSS and heap allocation trends for all bRPC workloads with alerting on sustained growth
  • Monitor HTTP/2 stream reset counts and HTTP 413 response rates after patching to confirm enforcement is active
  • Capture netflow or reverse-proxy logs for upstream bRPC endpoints to retain source IPs for abusive peers

How to Mitigate CVE-2026-61902

Immediate Actions Required

  • Upgrade all Apache bRPC deployments to version 1.18.0 or later
  • If upgrading is not immediately possible, apply the upstream patch from PR #3382 and rebuild affected services
  • Place bRPC services behind a reverse proxy or API gateway that enforces strict request body size limits
  • Set operating-system memory limits (for example, cgroup memory.max) on bRPC processes to contain impact

Patch Information

The fix is included in Apache bRPC 1.18.0. According to the project advisory, the patch rejects oversized buffered HTTP bodies, returns HTTP 413 for HTTP/1 requests, resets oversized HTTP/2 streams, and rejects oversized memcache and couchbase responses based on their declared lengths. Progressive HTTP reading remains supported because it already uses bounded buffering.

Workarounds

  • Terminate HTTP/1 and HTTP/2 traffic at a front-end proxy that enforces a maximum request body size smaller than available process memory
  • Restrict network reachability of bRPC services to trusted clients using firewall rules or service mesh policy until patching is complete
  • Switch client code to progressive HTTP reading where feasible, since that path uses bounded buffering and is not affected
bash
# Verify installed bRPC version and upgrade
git -C brpc describe --tags
git -C brpc fetch --tags
git -C brpc checkout 1.18.0
cmake -S brpc -B brpc/build -DCMAKE_BUILD_TYPE=Release
cmake --build brpc/build --target install

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.