CVE-2026-116567
🟠 MediumSignalWire FreeSWITCH, in mod_rtmp. The mitigating fact is in the record and matters more than either score: the module is disabled in the stock build and configuration, so a default FreeSWITCH is not exposed and only an estate that deliberately enabled RTMP is · Before 1.11.2
38.05th percentile
Exploitation
Timeline
- 05/11/2026CVE record published (CVE List)
Risk
mod_rtmp's control-message handler writes an RTMP user-control message into a 200-byte stack buffer with no bounds check, and a body of roughly 70 bytes or more overflows it before any login. The record states that control-flow hijacking has not been achieved, which is why the impact is availability-only)Fix
mod_rtmp is not enabled, which in a stock build it is notOfficial description
FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, rtmp_handle_control() rendered an RTMP user-control message into a 200-byte stack buffer using an unbounded sprintf loop controlled by the wire message length. A body of roughly 70 bytes or more overflowed the stack before any RTMP login, because the handshake authenticates neither side. The flaw affects deployments that build and load mod_rtmp, which is disabled in the stock build and configuration but commonly exposes a listener on TCP port 1935 when enabled. One unauthenticated message can crash FreeSWITCH and end every active call; the constrained ASCII hex output has not yielded control-flow hijacking. This issue is fixed in version 1.11.2.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE-121