FreeSWITCH heap buffer overflow in WebSocket frame unmasking
signalwire freeswitch
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| signalwire freeswitch |
| No fix yet |
Original 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, 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.
From the CVE record · GitHub_M
References
- github.com/signalwire/freeswitch/security/advisories/GHSA-4cg6-rvh2-cw74Vendor advisory
- github.com/signalwire/freeswitch/commit/fb9f37b9c7869630ee52a3ae87399fbbf99ad74dPatch
- github.com/signalwire/freeswitch/releases/tag/v1.11.2Release notes
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/116xxx/CVE-2026-116781.json
- nvd.nist.gov/vuln/detail/CVE-2026-116781