Quick answers
- Is CVE-2026-82953 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82953 being exploited in the wild.
- How severe is CVE-2026-82953?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- Apache Brpc < 1.18.0.
- Is there a fix for CVE-2026-82953?
- Yes: fixed in 1.18.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82953 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82953?
- Check whether you run Apache Brpc at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.18.0
Technical details
The vulnerability is a NULL pointer dereference in RtmpChunkStream::OnCreateStream() that occurs when RtmpService::NewStream() returns null (rejecting the stream) and the subsequent error response write fails. The error path attempts to access stream->_onfail_id on the null pointer, causing a crash. An attacker needs network access to the RTMP service and can trigger this by sending a crafted createStream command followed by an immediate disconnection.
Affected products
- Apache bRPC < 1.18.0
Timeline
- 2026-10-21: disclosed
- 2026-09-03: patched: PR #3508 merged to master