FreeSWITCH CVE-2026-116779: One SIP Message to Command Execution

FreeSWITCH powers a huge share of the world's VoIP. A single crafted inbound SIP MESSAGE can select an 'api' chat protocol that the server then executes as FreeSWITCH API commands, several of which reach the operating system. The result is unauthenticated command execution, rated CVSS 9.8 and already exploited in the wild. Here's the mechanism, the fix in 1.11.3, and how to catch it.

3 min readAdvanced

Executive summary. CVE-2026-116779 is a command-injection flaw in SignalWire FreeSWITCH, the open-source telephony platform behind countless PBXs, carriers and contact-centre stacks. A crafted inbound SIP MESSAGE can select FreeSWITCH's "api" chat protocol; the mod_dptools chat handler then passes the message straight to the API execution function, running FreeSWITCH API commands with the privileges of the FreeSWITCH process. Several of those commands reach the operating system, and on stock installs with mod_lua loaded there is a second route through inline Lua. It is rated CVSS 9.8, is exploited in the wild, and was added to the CISA KEV catalog on 9 November 2026. FreeSWITCH 1.11.3 fixes it. If you run FreeSWITCH with SIP exposed, treat this as patch-now.

FreeSWITCH SIP MESSAGE command injection flow

What it is

Field Detail
CVE CVE-2026-116779
Product SignalWire FreeSWITCH (open-source VoIP/telephony)
Affected FreeSWITCH through 1.11.2
Fixed in 1.11.3 (upstream commit 7015f6a)
Type Command injection via SIP MESSAGE / chat "api" protocol
Severity CVSS 9.8 (critical)
Status Exploited in the wild; CISA KEV (added 9 Nov 2026)

How it works

text
 Inbound SIP MESSAGE  ──►  chat proto = "api"
          │
          ▼
 mod_dptools chat handler  ──►  switch_api_execute(address, ...)
          │  runs a FreeSWITCH API command as the service
          ▼
 OS-reaching API commands (and mod_lua inline scripts)
          │
          ▼
 Command execution as the FreeSWITCH process
  • The trigger: an attacker who can deliver a SIP MESSAGE to a SIP profile can set the chat protocol to api. Nothing authenticates that choice on vulnerable builds.
  • The sink: mod_dptools forwards the message address to FreeSWITCH's API executor. FreeSWITCH API commands are powerful by design, and some of them (and mod_lua's inline Lua) reach the shell.
  • The result: arbitrary command execution as the FreeSWITCH service account, from a single unauthenticated message. No call needs to be answered.

Why it needs industry attention

FreeSWITCH sits at the edge of voice networks — often internet-reachable on SIP ports, often forgotten between audits, and often running as a privileged service. A VoIP server is a superb pivot: it talks to internal networks, holds call-detail data, and rarely has EDR. A wormable, unauthenticated RCE on that box is exactly the kind of thing that turns into toll fraud, eavesdropping or a foothold.

Fix and mitigation

  1. Upgrade to FreeSWITCH 1.11.3+. The fix adds a per-profile enable-chat-api-proto parameter that is off by default, and a MESSAGE selecting the api protocol is answered with a 403 and logged.
  2. Can't upgrade yet? Set enable-chat=false on any SIP profile that doesn't need inbound SIP chat. This reduces exposure but is not a full fix.
  3. Restrict the network. SIP ports should not be open to the whole internet; limit to known carriers/peers and put FreeSWITCH behind an SBC where possible.
  4. Drop privileges. Run FreeSWITCH as a non-root, least-privilege service so that even successful injection is contained.

How to detect it

  • Log hunting: on patched builds, watch for the new 403 responses to api-protocol MESSAGEs — that is someone trying. On any build, alert on FreeSWITCH spawning shells (sh, bash, lua, curl, wget) as children of the freeswitch process.
  • Behavioural: the FreeSWITCH service account making outbound connections or writing to /tmp and executing is a strong signal.
  • SIP telemetry: inbound MESSAGE methods carrying API-looking payloads to profiles that don't use chat.

Conclusion

CVE-2026-116779 is a reminder that messaging features on voice servers are code-execution surfaces. The fix is simple and already shipped; the risk is that FreeSWITCH boxes are easy to forget. Inventory every FreeSWITCH instance, patch to 1.11.3, disable chat where it isn't needed, and put a detection on the service spawning shells.

Do this now: find every FreeSWITCH host, confirm the version, upgrade to 1.11.3, set enable-chat=false on profiles that don't need it, and alert on the FreeSWITCH process spawning a shell.

Related: our network pentesting manual and the community thread on detecting services spawning shells.

Sources: Bitsight, Help Net / exeo.net, LinuxSecurity, OSV. Verify specifics against SignalWire's advisory and the CISA KEV entry.

HackersRoot Research · Research team

The HackersRoot research team investigates attack techniques across AI systems, cloud and identity, and enterprise networks, then publishes the detections and hardening guidance that stop them.

More from HackersRoot →

Related research

Vulnerability Intel

OpenSSH 'SSHole' (CVE-2026-123158): When a Long Password Becomes a Skeleton Key

SSHole (CVE-2026-123158) is an OpenSSH authentication bypass on Linux systems that use musl libc without PAM. An oversized password makes the hash computation fail and return an asterisk, which matches the locked-account placeholder in the shadow file, so sshd accepts the login. It was exploited within about nine hours of disclosure. Here's the mechanism, who is affected, and the fix.

Vulnerability Intel

Oracle PeopleSoft CVE-2026-35273: An Unauthenticated Door Into the HR Mainframe of the Enterprise

Oracle issued an out-of-band alert for CVE-2026-35273, a missing-authentication flaw in PeopleSoft PeopleTools' Environment Management hub (PSEMHUB). Reachable over HTTP with no credentials, it can lead to server-side request forgery and remote code execution. Mandiant tied zero-day exploitation to ShinyHunters (UNC6240) against higher education. Here's the mechanism and the response.

Vulnerability Intel

Zyxel GS1900 CVE-2026-107441: The Patch That Didn't Hold, and 996 Switches That Paid for It

In June, Zyxel patched a GS1900 switch flaw (CVE-2026-7273). But the fix didn't fully close it: Binarly found the exploit still worked, and GreyNoise saw data taken from around 996 switches in August. Zyxel reclassified the missing parameter-length validation as a new CVE, CVE-2026-107441, an out-of-bounds write giving unauthenticated root command execution. The real fix is 2.90 Patch 3.