---
id: "CVE-2026-61916"
kind: "vulnerability"
aliases: ["CVE-2026-61916"]
title: "bRPC: high-bit URL bytes crash the server on ARM64"
severity: "unknown"
cvss: null
epss: 0.00202
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-brpc", "arm64", "http-server", "http2", "package"]
not_affected_if: ["http1-only", "no-network-exposure", "x86_64-build"]
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:43+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-61916", "first_seen_at": "2026-10-23T21:57:28+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-61916", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# bRPC: high-bit URL bytes crash the server on ARM64

Apache bRPC reads past the end of two lookup tables when a request contains bytes with the high bit set, on platforms where plain char is unsigned such as ARM64. An remote attacker can crash the process, causing 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 against `1.18.0`.
- Determine whether the build target is ARM64 or another platform where plain char is unsigned; x86_64 builds are not affected per the sources.
- Check whether the server is an HTTP server reachable from untrusted clients, or uses HTTP/2 HPACK with untrusted header names.

## Fix

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

## Timeline

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

## From the sources

Out-of-bounds reads in URL parsing and case-insensitive header lookup in Apache bRPC before version 1.18.0 on platforms where plain char is unsigned, such as ARM64, allow remote attackers to cause a process crash and denial of service by sending crafted input containing bytes with the high bit set.

Root Cause:
Two 256-entry lookup tables are accessed through pointers biased by 128 so that valid indices are in the range -128 to 127. Input bytes are promoted from plain char to int without first normalizing them to the signed-char range. On affected platforms, bytes in the range 0x80 to 0xFF therefore become indices 128 to 255 and read up to 127 bytes beyond the end of the underlying tables.

Affected Scenarios:
A remotely accessible bRPC HTTP server on an affected platform can reach the vulnerable URL lookup through an unauthenticated request URI containing a high-bit byte. The case-insensitive lookup is also reachable when untrusted header names are processed through APIs such as the HTTP/2 HPACK path. HTTP/1 header names containing high-bit bytes are rejected by the HTTP/1 parser before reaching the vulnerable lookup. Builds where plain char is signed, which commonly include x86_64 builds, are not affected by this issue.

How to Fix:
Choose one of the following options:
1. Upgrade Apache bRPC to version 1.18.0 or later.
2. Apply the patch from  https://github.com/apache/brpc/pull/3376 .

The fix normalizes lookup-table indices to the signed-char range before accessing the biased tables.

---

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