# CVE-2026-116779: SignalWire FreeSwitch Code Injection


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 9 Nov 2026 (CISA KEV)
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-mg63-h38w-8p9p

## What is CVE-2026-116779?

CVE-2026-116779 is a critical vulnerability in signalwire freeswitch, published on 5 Nov 2026. 

### Official 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.3, sofia_presence_handle_sip_i_message() split the To user of an inbound SIP MESSAGE on a plus sign and treated the left side as a chat protocol selector. Selecting the api chat proto reached switch_api_execute(), allowing a peer whose MESSAGE was accepted to run FreeSWITCH API commands, including operating-system command sinks, with the daemon's privileges. Inbound chat is enabled on the stock internal and external profiles, and any authenticated profile account is sufficient; stock directory users without password material can also remove that barrier in affected configurations. The flaw permits configuration and credential disclosure, arbitrary call control, and command execution, and exploitation has been observed in the wild. This issue is fixed in version 1.11.3.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-749 (Exposed Dangerous Method or Function)

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

It affects 1 product.


Products: Freeswitch.

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

No fix has been published for CVE-2026-116779 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 12 Nov 2026.

## Is CVE-2026-116779 being exploited?

Yes. Attackers have exploited CVE-2026-116779 in the wild since at least 9 Nov 2026.

Public exploit code:

- https://github.com/hackzuoji/freeswitch-cve-2026-116779-POC (github_poc): https://github.com/hackzuoji/freeswitch-cve-2026-116779-POC
- 🚨 CVE ID: CVE-2026-116779 📦 Product: FreeSWITCH 💉 Type: Command Injection (via SIP MESSAGE) 🔥 Score: 9.8 (Critical(RCE)) +20K target  (github_poc): https://github.com/majidrahimi5020-lgtm/Poc-exploit-for-CVE-2026-116779-FreeSWITCH-

## Other vulnerabilities in signalwire freeswitch

- [CVE-2026-49841](https://insights.sbomify.com/CVE-2026-49841/): FreeSWITCH: Pre-authentication heap buffer overflow in `mod_verto` HTTP POST body read (critical 9.8)
- [CVE-2019-19492](https://insights.sbomify.com/CVE-2019-19492/): FreeSWITCH 1.6.10 through 1.10.1 has a default password in event_socket.conf.xml. (critical 9.8)
- [CVE-2026-116785](https://insights.sbomify.com/CVE-2026-116785/): FreeSWITCH: Pre-authentication heap out-of-bounds write in mod_xml_rpc WebSocket frame length handling (critical 9.1)
- [CVE-2026-116790](https://insights.sbomify.com/CVE-2026-116790/): FreeSWITCH: Inbound ICE connectivity checks are accepted without verifying STUN MESSAGE-INTEGRITY (critical 9.1)
- [CVE-2026-49840](https://insights.sbomify.com/CVE-2026-49840/): FreeSWITCH: Pre-authentication heap buffer overflow in libesl `Content-Length` parsing (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116779 and fix it if it is affected.

What it is: CVE-2026-116779 is a critical vulnerability in signalwire freeswitch, published on 5 Nov 2026. 
Exploitation: Yes. Attackers have exploited CVE-2026-116779 in the wild since at least 9 Nov 2026.

Affected product: signalwire freeswitch. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116779/ (Markdown: https://insights.sbomify.com/CVE-2026-116779/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116779
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116779
- OSV: https://osv.dev/vulnerability/CVE-2026-116779

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116779/
Summaries are generated and may contain mistakes; the official description above is the record.