Skip to main content
← Vulnerabilities

FreeSWITCH: Heap out-of-bounds read in FreeSWITCH core variable expansion via `${variable:offset}` slicing

2.7LowCNA
Exploited
No known exploitation
Fix
Fixed in 1.11.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.11.2.

Published
Last modified
6/100 · provisional
None on Exploit-DB, Metasploit or GitHub

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.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the 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, 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.

cve.now Index

6Pcve.now Index 6 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity2.7/10CVSS 2.7
  • No patch0/5No signal

What would change the score

  • Would score about 61 if added to CISA KEV
  • Would score about 56 if CISA's SSVC rates exploitation active
  • Would score about 25 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.11.2.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • signalwire freeswitch

    fixed in 1.11.2

Evidence 3

  1. Advisory
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-116780

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: cve.now feed data

Which versions are affected by CVE-2026-116780?

freeswitch: before 1.11.2.Source: cve.now feed data

How do I fix CVE-2026-116780?

Upgrade to a fixed version: 1.11.2.Source: cve.now feed data