Live › vulnerability › CVE-2026-61916
Go to dashboardApache 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Affected systems are remotely reachable bRPC HTTP servers built on platforms where plain char is unsigned, such as ARM64. Exposure also applies where untrusted header names pass through the case-insensitive lookup, such as the HTTP/2 HPACK path. HTTP/1 header names with high-bit bytes are rejected earlier, and x86_64 builds where plain char is signed are not affected.
No product ranges from the sources yet.
1.18.0.1.18.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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:
The fix normalizes lookup-table indices to the signed-char range before accessing the biased tables.
This page as .md · .json · in your agent: get_signal("CVE-2026-61916")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.