# CVE-2026-54426: Apache bRPC: Stack Exhaustion via Unbounded Recursion in Redis Reply Parser


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-m7v5-m3p2-6w26

## What is CVE-2026-54426?

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

### Official description

Uncontrolled recursion in the Redis reply parser in Apache bRPC < 1.18.0 allows a remote Redis server peer to crash a bRPC Redis client process by returning a deeply nested RESP array reply. The parser recursed once for each nested array level without enforcing a depth limit. The fix adds a configurable Redis reply depth limit with default value 128 and rejects replies exceeding that limit. 

Affected Scenarios:
Applications using bRPC as a Redis client with ChannelOptions.protocol="redis" and receiving replies from an untrusted or faulty Redis server peer.

How to Fix:
1. Upgrade Apache bRPC to 1.18.0.
2. Apply the patch from PR  https://github.com/apache/brpc/pull/3344 .

Note:
After applying the fix, Redis replies with array nesting deeper than redis_max_reply_depth are rejected.

Weakness: CWE-674 (Uncontrolled Recursion)

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


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

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

## Is CVE-2026-54426 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54426 is a vulnerability in Apache bRPC, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-54426 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-54426/ (Markdown: https://insights.sbomify.com/CVE-2026-54426/index.md)
```

## Sources

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

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