# CVE-2026-82210: Apache bRPC: Remote denial of service (crash) via malformed stream feedback frames


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-f22p-qq49-qcxh

## What is CVE-2026-82210?

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

### Official description

Enforceable assertion in the streaming feature of Apache bRPC (version < 1.18.0) on all platforms allows a remote attacker to crash the server process by sending a malformed stream feedback frame.

Root Cause:
When handling FRAME_TYPE_FEEDBACK frames, bRPC calls Stream::SetRemoteConsumed() which contains CHECK(_cur_buf_size > 0) and unconditionally asserts CHECK(buf.IsEmpty()) on the frame payload. A feedback frame that carries an unexpected payload, or a feedback frame received on a stream where flow control is disabled (cur_buf_size == 0), reaches these assertions. On failure, CHECK failures abort the process, allowing an unauthenticated single client (once a stream is established) to terminate the server and cause a denial of service.

Affected Scenarios:
Use bRPC server with the streaming control feature (Stream API) served from untrusted network.

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

The fix rejects malformed feedback frames with EPROTO and closes only the affected stream instead of crashing the whole process, and it bounds buffer shrinking so cur_buf_size never drops to 0 while flow control is enabled.

Weakness: CWE-617 (Reachable Assertion)

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


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

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

## Is CVE-2026-82210 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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