CVE-2026-84727: Use-after-free in the RTMP protocol implementation in Apache bRPC (version RtmpChunkStream::SerializeMessage) runs concurrently on sender threads and…

PriorityP432medium5.4CVSS 3.1

AVNACLPRLUINSUCNILAL

EPSS

0.32%

24.1th percentile

Use-after-free in the RTMP protocol implementation in Apache bRPC (version RtmpChunkStream::SerializeMessage) runs concurrently on sender threads and dereferences the same RtmpChunkStream object without synchronization. If a remote peer sends an Abort message naming a chunk stream that is concurrently being used to serialize an outgoing message, the stream object is freed while still in use, resulting in a use-after-free. Additionally, deleting the chunk stream discarded its previous message header, so subsequent compressed (type-3) chunk headers on that stream could no longer be decoded. Affected Scenarios: Any application using the bRPC RTMP protocol implementation (rtmp policy), either as an RTMP server or as an RTMP client, where the remote endpoint is untrusted. The attacker needs to send an Abort message targeting a chunk stream id that is concurrently used for sending, which can crash the process or lead to memory corruption. 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/3515

Affected

1 ranges

Vendor	Product	Version range	Fixed in
apache_software_foundation	apache_brpc	< 1.18.0	1.18.0

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.