# CVE-2026-58064: Apache bRPC: Denial of Service via Unbounded Redis Inline Command Allocation


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-m3mv-32pp-6vgx

## What is CVE-2026-58064?

CVE-2026-58064 is a vulnerability in Apache bRPC, published on 21 Oct 2026. 

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-58064?


## How do I fix CVE-2026-58064?

No fix has been published for CVE-2026-58064 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-58064 being exploited?

There is no known exploitation of CVE-2026-58064 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58064 and fix it if it is affected.

What it is: CVE-2026-58064 is a vulnerability in Apache bRPC, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-58064 in the wild and no public exploit code.

Affected product: Apache bRPC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58064/ (Markdown: https://insights.sbomify.com/CVE-2026-58064/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58064
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58064
- OSV: https://osv.dev/vulnerability/CVE-2026-58064

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58064/
Summaries are generated and may contain mistakes; the official description above is the record.