Medium [CVE-2026-84727] 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
This medium-severity Apache Software Foundation advisory covers CVE-2026-84727; 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
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:
- Apache bRPC before 1.18.0
Official advisory · high-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/3515
Official advisory · high-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.