CVE-2026-116781 · Runtime
NO FIX YET · SEE WHAT TO DO
FreeSWITCH's WebSocket reader unmasks payload using the wrong length, so a masked frame can write up to 14 bytes past a 64 KiB buffer. An attacker who can reach the endpoint before logging in may corrupt adjacent memory; no crash or data disclosure has been demonstrated.
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.
Only deployments that enable mod_xml_rpc and its opt-in WebSocket endpoint are exposed; both are disabled in the stock configuration. Systems that keep those features off, or that cannot reach the endpoint from untrusted networks, can skip it. The sources say the writes stay inside the same connection's outbound buffer.
Not affected if default-config, mod-xml-rpc-disabled, websocket-disabled
Who cares freeswitch, self-hosted, telecom, voip
fs_cli -x version and compare it to the fixed release.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, ws_read_frame() unmasked a WebSocket payload by iterating wsh->datalen, which included frame headers, while indexing from the payload pointer. A masked frame filling the 64 KiB receive buffer could therefore XOR up to 14 bytes beyond the buffer, and the exact-capacity case also wrote a terminating NUL one byte out of bounds. The flaw is reachable before authentication when mod_xml_rpc and its opt-in WebSocket endpoint are enabled, while both features are disabled in the stock configuration. The writes remain within the same connection handle's adjacent outbound buffer, so neither a process crash nor cross-session disclosure has been demonstrated. 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.