Quick answers
- Is CVE-2026-116785 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116785 being exploited in the wild.
- How severe is CVE-2026-116785?
- Critical severity, with a CVSS score of 9.1, published 5 November 2026.
- Which products and versions are affected?
- SignalWire FreeSWITCH prior to 1.11.2.
- Is there a fix for CVE-2026-116785?
- Yes: fixed in 1.11.2. Until then: Disable mod_xml_rpc and the WebSocket endpoint (both are disabled by default). If these modules must be enabled, restrict network access to trusted clients only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116785 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-116785?
- Check whether you run SignalWire FreeSWITCH at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.11.2
Disable mod_xml_rpc and the WebSocket endpoint (both are disabled by default). If these modules must be enabled, restrict network access to trusted clients only.
Technical details
The ws_read_frame() function in mod_xml_rpc incorrectly decodes the 64-bit WebSocket extended payload length using a 32-bit byte swap (ntohl), then narrows it to a signed length that bypasses validation and is reinterpreted as an enormous unsigned value. This causes heap buffer overwrite beyond the 64 KiB receive buffer, corrupting connection state and crashing the process. The attack requires network access and completion of a WebSocket upgrade on the /socket endpoint, but both the module and endpoint are disabled by default, and HTTP authentication is not required.
Affected products
- SignalWire FreeSWITCH prior to 1.11.2
Timeline
- 2026-11-05: disclosed