CVE-2026-82210
UNSCOREDDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3.1 Vector
No CVSS vector data available.
Exploit Intelligence
Low risk: more likely to be exploited than 8% of all known CVEs.
References
Related Vulnerabilities
Other CWE-617 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2015-5477 | High | 7.5 | 99% | KEV | Fix |
| CVE-2020-8617 | High | 7.5 | 93% | - | Fix |
| CVE-2020-36222 | High | 7.5 | 77% | - | Fix |
| CVE-2006-5779 | High | 7.5 | 77% | - | Fix |
| CVE-2021-27212 | High | 7.5 | 66% | - | Fix |
| CVE-2018-5740 | High | 7.5 | 60% | - | Fix |
Common questions
How do I fix CVE-2026-82210?
No published fix for CVE-2026-82210 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-82210 being actively exploited?
Not that we know of. CVE-2026-82210 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.19% is the estimated probability that it will be exploited in the next 30 days. That is higher than 8% of all scored CVEs.
Embed a live status badge for CVE-2026-82210
Markdown
[](https://tridentstack.com/cve/CVE-2026-82210)HTML
<a href="https://tridentstack.com/cve/CVE-2026-82210"><img src="https://tridentstack.com/cve/badge/CVE-2026-82210.svg" alt="CVE-2026-82210"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-22.