CVE Catalog

CVE-2026-116567

HighCVSS 7.5
Published: Updated: Translated: NVD NIST

Summary

In FreeSWITCH before 1.11.2, rtmp_handle_control() renders 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 overflows 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 but commonly exposes a listener on TCP port 1935 when enabled.

Risk Assessment

An unauthenticated attacker can crash FreeSWITCH with a single message and terminate every active call. Control-flow hijacking has not been demonstrated, but service availability is severely impacted.

Recommendation

Upgrade FreeSWITCH to version 1.11.2 or later. If mod_rtmp is not required, disable it and block access to TCP port 1935 at the firewall.

Other vulnerabilities in FreeSWITCH

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS