CVE-2026-116780signalwire freeswitch out-of-bounds read
CVE-2026-116780 is a out-of-bounds read in signalwire freeswitch, rated low (2.7 on CVSS 3.1).
Why this priority: Low severity, with no exploitation signal.
Published · Updated · NVD status: Analyzed
What it is
Code reads past the end of a buffer, leaking memory contents or crashing. The software reveals data to someone who should not see it.
How it is reached
An attacker can exploit it over the network, with an administrator account, and nobody has to click anything.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker crash the process, read memory, or in the worst case run code.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade signalwire freeswitch to 1.11.2 or later. The patch notes are linked below.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
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 this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Native code: operating systems, browsers and firmware. The flaw sits wherever native code reads untrusted data.
- Network appliances and media or file parsers. The flaw sits wherever native code reads untrusted data.
- Error responses, logs and debug endpoints. The flaw sits between internal data and whoever can read the response or log.
- APIs that over-share. The flaw sits between internal data and whoever can read the response or log.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Wherever native code reads untrusted data. An attacker who crosses it can crash the process, read memory, or in the worst case run code.
- Between internal data and whoever can read the response or log. An attacker who crosses it can learn data or internals that help a follow-up attack.
Questions to answer about your own systems
- Where does signalwire freeswitch run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.