---
id: "CVE-2026-58064"
kind: "vulnerability"
aliases: ["CVE-2026-58064"]
title: "Apache bRPC: inline Redis parsing allocates whole buffer, enabling memory denial of service"
severity: "medium"
cvss: null
epss: 0.00202
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["apache-brpc", "redis-protocol", "runtime", "self-hosted"]
not_affected_if: ["internal-only-network", "redis-protocol-disabled"]
published_at: "2026-10-21T12:17:21+00:00"
first_seen_at: "2026-10-23T21:57:28+00:00"
updated_at: "2026-10-25T05:02:48+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-58064", "first_seen_at": "2026-10-23T21:57:28+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-58064", "first_seen_at": "2026-10-24T13:15:54+00:00"}]
---

# Apache bRPC: inline Redis parsing allocates whole buffer, enabling memory denial of service

The Redis protocol handler in Apache bRPC copies the entire connection buffer for inline commands before a complete CRLF-terminated line arrives. A remote client can send long inline input without a terminator to drive up memory use and CPU copy overhead, causing denial of service.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether the bRPC server is built with Redis protocol support and listens on a port reachable by untrusted clients.
- Run `grep -rn redis_max_allocation_size` in the bRPC source or config to see whether the limit is set.

## Fix

- Upgrade Apache bRPC to `1.18.0`.
- Or apply the patch from https://github.com/apache/brpc/pull/3363.

## Timeline

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

## From the sources

The Redis protocol implementation in Apache bRPC allowed inline command parsing to allocate and copy the full connection buffer before a complete CRLF-terminated command was available. A remote attacker with access to a Redis-protocol bRPC service could send long inline inputs without a terminating CRLF to increase memory usage and CPU copy overhead, potentially causing denial of service.


Root Cause:
The Redis inline command parser allocated memory based on the current input buffer size and copied the entire buffer before determining the current inline command boundary. The existing redis_max_allocation_size limit was applied to RESP bulk strings and arrays, but not effectively to the inline command path before allocation.


Affected Scenarios:
Use Apache bRPC server with Redis protocol enabled and reachable by untrusted clients.


How to Fix:
1. Upgrade Apache bRPC to version 1.18.0, which fixes this issue.
2. Apply the patch from PR  https://github.com/apache/brpc/pull/3363 .


Note:
The fix applies redis_max_allocation_size to Redis inline command lines and scans for CRLF before allocating parser arena memory. Inline command lines exceeding this limit are rejected.

---

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