Advisory [CVE-2026-82425] 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
This security Apache Software Foundation advisory covers CVE-2026-82425; related products: Apache bRPC.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Apache Software Foundation publishes the next one.
VulniPulse checks Apache Software Foundation's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.
Summary
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:
Note:
- Apache bRPC before 1.18.0
Official advisory · medium-confidence parse· fetched 7 days ago·verify at source
- 1.18.0
Official advisory · medium-confidence parse· fetched 7 days ago·verify at source
Mitigation checklist
- Upgrade bRPC to version 1.18.0, which fixes this issue.
- 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.
Official advisory · medium-confidence parse· fetched 7 days ago·verify at source
More Apache Software Foundation advisories
- CVE-2026-90484Oct 21, 2026The MySQL client response parser in Apache bRPC dereferences a null pointer
- CVE-2026-87849Oct 21, 2026The Discovery naming-service reply parser in Apache bRPC (versions < 1.18.0) calls
- CVE-2026-86249Oct 21, 2026On a brpc::Server that sets both ServerOptions.auth and ServerOptions.internal_port
- CVE-2026-86147Oct 21, 2026External control of file name or path and uncontrolled resource consumption in Apache bRPC
- CVE-2026-86146Oct 21, 2026Inconsistent interpretation of HTTP requests (HTTP request/response smuggling)
- CVE-2026-84748Oct 21, 2026Improper authorization in Apache bRPC (versions < 1.18.0) on all platforms allows remote
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.