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

CVE-2026-61916: Apache bRPC Out-of-Bounds Read DOS Vulnerability

CVE-2026-61916 is an out-of-bounds read vulnerability in Apache bRPC affecting ARM64 platforms that allows remote attackers to crash processes. This post 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-61916 Overview

CVE-2026-61916 is an out-of-bounds read vulnerability [CWE-125] in Apache bRPC versions prior to 1.18.0. The flaw affects URL parsing and case-insensitive HTTP header lookups on platforms where plain char is unsigned, such as ARM64. Remote attackers can crash a bRPC HTTP server by sending a request containing bytes with the high bit set, resulting in denial of service. The vulnerable code paths are reachable without authentication through the request URI and through HTTP/2 HPACK header names.

Critical Impact

Unauthenticated remote attackers can crash Apache bRPC HTTP servers running on ARM64 or other platforms where plain char is unsigned, producing denial of service with a single crafted request.

Affected Products

  • Apache bRPC versions prior to 1.18.0
  • Builds on platforms where plain char is unsigned, including ARM64
  • bRPC HTTP servers accepting HTTP/1 request URIs or HTTP/2 HPACK header names

Discovery Timeline

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

Technical Details for CVE-2026-61916

Vulnerability Analysis

Apache bRPC uses two 256-entry lookup tables for URL character classification and case-insensitive header name comparison. These tables are accessed through pointers biased by 128, so valid indices span the signed-char range of -128 to 127. The parser promotes input bytes from plain char to int without first narrowing them to the signed-char range. On platforms where plain char is unsigned, high-bit bytes in the range 0x80 to 0xFF become positive integer indices 128 to 255. The lookup then reads up to 127 bytes beyond the end of the backing table, causing undefined behavior and typically a process crash.

Root Cause

The root cause is an improper type-promotion assumption in the lookup logic. The code assumes plain char is signed, which holds on x86_64 but not on ARM64 and other platforms where plain char is unsigned. Because the biased table pointer is offset by 128, only indices within -128 to 127 remain inside the allocated 256-byte region. Out-of-range indices translate directly to out-of-bounds memory reads.

Attack Vector

An unauthenticated remote attacker sends an HTTP request to a bRPC HTTP server with a request URI containing any byte in 0x80-0xFF. The crafted byte reaches the vulnerable URL lookup and triggers the out-of-bounds read. The case-insensitive header lookup is also reachable when untrusted header names traverse the HTTP/2 HPACK decoder. HTTP/1 header names with high-bit bytes are rejected by the HTTP/1 parser before reaching the vulnerable code. Builds where plain char is signed, including typical x86_64 builds, are not affected. See the Apache Security Announcement for upstream details.

Detection Methods for CVE-2026-61916

Indicators of Compromise

  • Unexpected crashes or restarts of bRPC server processes on ARM64 hosts following inbound HTTP traffic.
  • Core dumps referencing the URL parsing or case-insensitive header lookup functions in bRPC.
  • HTTP access logs containing request URIs or HTTP/2 HPACK header names with non-ASCII bytes (0x80-0xFF).

Detection Strategies

  • Inventory running Apache bRPC instances and verify both the version (< 1.18.0) and the host architecture to identify exposed ARM64 builds.
  • Alert on process termination signals (SIGSEGV, SIGBUS) for bRPC services and correlate against inbound HTTP request logs.
  • Inspect HTTP/2 traffic to bRPC endpoints for HPACK header names containing high-bit bytes, which should not occur in legitimate traffic.

Monitoring Recommendations

  • Collect and centralize bRPC service logs, crash dumps, and systemd restart counters for anomaly detection.
  • Monitor upstream reverse proxies for abnormal rates of client-closed or reset HTTP connections toward bRPC backends.
  • Baseline normal request URI byte distributions and alert when non-ASCII bytes appear in URIs sent to bRPC services.

How to Mitigate CVE-2026-61916

Immediate Actions Required

  • Upgrade Apache bRPC to version 1.18.0 or later on all affected platforms.
  • If immediate upgrade is not possible, apply the upstream patch from apache/brpc PR #3376 and rebuild.
  • Prioritize ARM64 builds and any build toolchain where plain char defaults to unsigned.

Patch Information

The fix in Apache bRPC 1.18.0 normalizes lookup-table indices to the signed-char range before accessing the biased tables. This ensures that any input byte produces an index within -128 to 127, keeping all reads inside the 256-byte backing storage. Patch details are available in the Apache bRPC pull request #3376.

Workarounds

  • Place a reverse proxy or web application firewall in front of bRPC HTTP endpoints and reject request URIs containing bytes in 0x80-0xFF.
  • Filter or reject HTTP/2 HPACK header names containing non-ASCII bytes before they reach the bRPC HPACK decoder.
  • Where feasible, rebuild bRPC with a compiler flag forcing plain char to be signed (for example, -fsigned-char on GCC/Clang) as a temporary architectural mitigation.
bash
# Example upstream mitigation: rebuild bRPC with signed char semantics
export CFLAGS="-fsigned-char"
export CXXFLAGS="-fsigned-char"
cmake -S . -B build
cmake --build build -j

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.