CVE-2026-116784 · Runtime
NO FIX YET · SEE WHAT TO DO
FreeSWITCH before 1.11.2 trusts an RTCP NACK packet's declared length when parsing feedback entries, so a short packet can make it read far past its 16 KiB receive buffer. A remote peer sending RTCP to an active video call can crash FreeSWITCH and end every call on it, though the flaw gives no write access.
first public Oct 28, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Any FreeSWITCH deployment that handles video calls is exposed, since the malicious RTCP packets must reach an active video call. Deployments on versions before 1.11.2 should treat this as relevant, especially those accepting calls from untrusted peers on the internet. Systems running audio-only calls with no video RTCP may be less exposed, but the sources do not say this removes the risk entirely.
Not affected if audio-only-calls, version-1.11.2-or-later
Who cares freeswitch, telecom, video-calls, voip
fs_cli -x version or freeswitch -version; anything below 1.11.2 is affected.1.11.2.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, process_rtcp_report() used an RTPFB NACK packet's declared RTCP header length as its feedback-entry loop bound instead of the datagram length already validated by the caller. A short packet with an oversized declaration could drive reads far beyond the fixed 16 KiB receive buffer. Any peer able to send RTCP to an active video call can reach the flaw, including calls where remote SDP enables video RTCP even though the SIP profile has no explicit RTCP interval configured. The out-of-bounds read can crash FreeSWITCH and terminate every active call, but supplies no write primitive and does not echo the read values to the sender. This issue is fixed in version 1.11.2.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.