# CVE-2026-82425: Apache bRPC: Reachable Assertion in Socket::OnInputEvent Allows Remote Denial of Service


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-j7g4-mmgg-8fg5

## What is CVE-2026-82425?

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

### Official description

A reachable assertion in Apache bRPC (version < 1.18.0) on all platforms allows a malicious remote peer to crash the process, resulting in denial of service.

Root Cause:
When a Socket with health checking enabled fails, Socket::WaitAndReset closes its file descriptor while the event dispatcher may still be delivering an input event (EPOLLIN/EVFILT_READ) that was fetched for the just-closed fd. If the health check then succeeds and revives the Socket, Socket::Address succeeds again while the fd is still -1 (the next write reconnects on demand). In that window, Socket::OnInputEvent hits CHECK(!(events & EPOLLIN)) (or the kqueue equivalent) because the Socket is addressable but has no fd. CHECK failures terminate the process when bRPC is built with glog or when the gflag -crash_on_fatal_log is enabled (CHECK always terminates in OFFICIAL_BUILD/NDEBUG builds as well).

Affected Scenarios:
Applications using bRPC clients with health check enabled (-health_check_interval). A malicious remote peer that the client connects to can deliberately abort connections and immediately accept the health check probes, racing connection teardown against health check revival to trigger the assertion and abort the process.

How to Fix:
(Choose one of the following options)
1. Upgrade bRPC to version 1.18.0, which fixes this issue.
2. Apply this patch:  https://github.com/apache/brpc/pull/3510 

Note:
After applying the fix, stale input events on a Socket revived without an fd are silently dropped instead of triggering the assertion. No user-visible interface or wire protocol is changed.

Weakness: CWE-617 (Reachable Assertion)

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


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

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

## Is CVE-2026-82425 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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