{"id":"CVE-2026-84727","kind":"vulnerability","aliases":["CVE-2026-84727"],"related":[],"title":"bRPC: RTMP abort message frees a chunk stream still in use","description":"Use-after-free in the RTMP protocol implementation in Apache bRPC (version < 1.18.0) on all platforms allows a malicious RTMP peer to crash the process or potentially corrupt memory via a crafted Abort message.\n\nRoot Cause:\nWhen processing an RTMP Abort (protocol control message type 2), the RTMP policy implementation deleted the target RtmpChunkStream object. The send path (RtmpUnsentMessage::AppendAndDestroySelf -> 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.\n\nAffected Scenarios:\nAny 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.\n\nHow to Fix:\n(Choose one of the following options)\n1. Upgrade bRPC to version 1.18.0, which fixes this issue.\n2. Apply this patch:  https://github.com/apache/brpc/pull/3515","summary":"A remote RTMP peer can send a crafted Abort control message that frees a chunk stream object while another thread is still using it. This use-after-free can crash the process or potentially corrupt memory.","severity":"medium","cvss":5.4,"epss":0.00323,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["brpc","c++","package","rtmp","self-hosted"],"not_affected_if":["brpc-1.18.0-or-later","rtmp-not-used"],"how_to_check":"- Check the bRPC version in use: `grep -rn \"BRPC_VERSION\\|brpc\" CMakeLists.txt` or the pinned version in your package manifest\n- Confirm whether the service enables the RTMP protocol (the rtmp policy) as a server or client","fix":"- Upgrade bRPC to `1.18.0` or later\n- Or apply the patch from https://github.com/apache/brpc/pull/3515","status":"open","published_at":"2026-10-21T13:20:03+00:00","first_seen_at":"2026-10-23T21:57:28+00:00","triaged_at":"2026-10-25T04:14:35+00:00","updated_at":"2026-10-25T04:14:35+00:00","category":"package","confidence":0.7,"triage":{"at":"2026-10-25T04:14:35Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade bRPC to `1.18.0` or later\n- Or apply the patch from https://github.com/apache/brpc/pull/3515","reach":"internet","title":"bRPC: RTMP abort message frees a chunk stream still in use","impact":"medium","summary":"A remote RTMP peer can send a crafted Abort control message that frees a chunk stream object while another thread is still using it. This use-after-free can crash the process or potentially corrupt memory.","category":"package","nicknames":[],"who_cares":["brpc","c++","rtmp","self-hosted"],"confidence":0.7,"needs_auth":"no","worst_case":"Remote peer crashes the process or corrupts memory","analyst_note":"","how_to_check":"- Check the bRPC version in use: `grep -rn \"BRPC_VERSION\\|brpc\" CMakeLists.txt` or the pinned version in your package manifest\n- Confirm whether the service enables the RTMP protocol (the rtmp policy) as a server or client","needs_analyst":false,"not_affected_if":["rtmp-not-used","brpc-1.18.0-or-later"],"who_is_affected":"Applications that use bRPC's RTMP protocol implementation, either as an RTMP server or as an RTMP client, where the remote endpoint is untrusted. Services that do not use the RTMP protocol path are not exposed through this flaw.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"medium"},"cost_usd":0.00064,"input_tokens":3791,"output_tokens":522,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-2026':13A,16A '-3':190C '-84727':14A,17A '/apache/brpc/pull/3515':283C '1':267C '1.18.0':75C,272C '2':108C,277C 'abort':3A,33B,95C,103C,144C,235C 'addit':176C 'affect':201C 'allow':79C 'anoth':43B 'apach':72C 'appendanddestroyself':122C 'appli':278C 'applic':204C 'attack':230C 'brpc':1A,18B,73C,207C,269C 'c':19B 'caus':98C 'choos':261C 'chunk':7A,39B,148C,179C,191C,239C 'client':222C 'compress':188C 'concurr':126C,152C,244C 'control':34B,105C 'corrupt':60B,90C,257C 'could':196C 'craft':32B,94C 'crash':55B,85C,250C 'cve':12A,15A 'decod':200C 'delet':113C,177C 'derefer':131C 'discard':181C 'either':213C 'endpoint':226C 'fix':260C,274C 'follow':265C 'free':5A,37B,53B,65C,175C 'freed':164C 'github.com':282C 'github.com/apache/brpc/pull/3515':281C 'header':185C,192C 'host':24B 'id':241C 'implement':70C,112C,210C 'issu':276C 'lead':254C 'longer':198C 'malici':81C 'memori':61B,91C,256C 'messag':4A,35B,96C,106C,145C,159C,184C,236C 'name':146C 'need':231C 'object':41B,117C,135C,162C 'one':262C 'option':266C 'outgo':158C 'packag':20B 'patch':280C 'path':120C 'peer':28B,83C,141C 'platform':78C 'polici':111C,212C 'potenti':59B,89C 'previous':183C 'process':57B,87C,100C,252C 'protocol':69C,104C,209C 'remot':26B,140C,225C 'result':169C 'root':97C 'rtmp':2A,21B,27B,68C,82C,102C,110C,208C,211C,216C,221C 'rtmpchunkstream':116C,123C,134C 'rtmpunsentmessag':121C 'run':125C 'scenario':202C 'self':23B 'self-host':22B 'send':30B,119C,142C,233C,247C 'sender':128C 'serial':156C 'serializemessag':124C 'server':217C 'still':9A,46B,166C 'stream':8A,40B,149C,161C,180C,195C,240C 'subsequ':187C 'synchron':137C 'target':115C,237C 'thread':44B,129C 'type':107C,189C 'untrust':228C 'upgrad':268C 'use':11A,47B,51B,63C,154C,168C,173C,205C,245C 'use-after-fre':50B,62C,172C 'version':74C,271C 'via':92C 'without':136C","nicknames":[],"mitigations":[],"who_affected":"Applications that use bRPC's RTMP protocol implementation, either as an RTMP server or as an RTMP client, where the remote endpoint is untrusted. Services that do not use the RTMP protocol path are not exposed through this flaw.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-21T13:20:03+00:00","kev":null,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L","cvss_by":"134c704f-9b21-4f2e-91b3-4a467353bcc0","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-84727","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-84727","severity":null,"published_at":"2026-10-21T13:20:03+00:00","modified_at":"2026-10-22T16:56:37+00:00","first_seen_at":"2026-10-23T21:57:28+00:00","fetched_at":"2026-10-23T22:29:01+00:00","note":null},{"source":"epss","external_id":"CVE-2026-84727","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-84727","severity":null,"published_at":null,"modified_at":null,"first_seen_at":"2026-10-24T13:15:54+00:00","fetched_at":"2026-10-24T13:15:54+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}