CVE-2026-116779: A Critical FreeSWITCH Flaw Turns SIP Messages Into Command Execution

mse major security alert blog
emma-stevens-bio-portrait
Written by Emma Stevens
Senior Threat Intelligence Advisor

Key takeaways for CVE-2026-116779

  • CVE-2026-116779 affects SignalWire FreeSWITCH versions through 1.11.2. SignalWire rated it Critical with a CVSS 3.1 score of 9.8, Bitsight’s threat intelligence report assigns it a DVE score of 10.0/10.
  • A crafted inbound SIP MESSAGE can select FreeSWITCH’s api chat protocol. This lets the server execute API commands with the privileges of the FreeSWITCH process, potentially opening the door to OS command execution, configuration and credential disclosure, and call manipulation.
  • SignalWire says exploitation has been observed in the wild. CISA added the vulnerability to its Known Exploited Vulnerabilities (KEV) catalog on November 9. Public proof-of-concept code has also appeared in public repositories.
  • Inbound chat is enabled by default in the stock internal and external profiles. Where message authentication is required, an attacker needs access to a valid account on that profile. The stock vanilla directory also includes users without password material; depending on configuration, those users may allow access without separate credentials.
  • The best fix is to upgrade to FreeSWITCH 1.11.3 or later. If patching takes time, set enable-chat=false on any profile that does not need inbound SIP chat. The FreeSWITCH inbound ACL and message authentication alone do not close the attack path.

What happened?

On October 28, SignalWire released an advisory about a flaw in how FreeSWITCH parses inbound SIP MESSAGE requests. Versions through 1.11.2 are affected, and version 1.11.3 includes the fix. SignalWire says exploitation has been observed in the wild, though it has not shared technical details about those attacks. CISA added CVE-2026-116779 to its Known Exploited Vulnerabilities catalog on November 9. This addition is a reason for organizations to prioritize patching, especially for servers reachable over public networks or supporting critical telephony services.

Proof-of-concept code has also appeared in public repositories. These repositories can lower the technical bar for potential attackers, but their presence alone does not establish that the code works or reflects the attacks SignalWire observed. The vendor has not commented on the reliability of those repositories.

How CVE-2026-116779 works

Under the hood, FreeSWITCH’s sofia_presence_handle_sip_i_message() function splits the user portion of the SIP MESSAGE “To” field at a plus sign, treating the left side as the name of a chat protocol. An attacker can craft an address that selects the api protocol. FreeSWITCH’s mod_dptools module registers that protocol and passes the selected API address to switch_api_execute(), which runs FreeSWITCH API commands. Because certain API commands can interact with the underlying operating system, successful exploitation can result in command execution with the privileges of the FreeSWITCH process.

This flaw lets inbound messages invoke FreeSWITCH API commands. SignalWire says an attacker could disclose configuration and credentials or manipulate calls. If mod_lua is loaded, as it is in the stock configuration, inline Lua scripts with access to the full standard library provide another route to command execution. The real-world impact depends on the permissions assigned to the FreeSWITCH service and its environment.

Understanding severity and exposure

SignalWire rates the flaw Critical with a CVSS 3.1 score of 9.8, citing a network attack vector, low complexity, no required user interaction, and no required privileges. Bitsight assigns it a DVE score of 10.0/10, reflecting its severity alongside reported exploitation and threat actor interest. Out of the box, FreeSWITCH leaves chat processing active across stock internal and external profiles unless an administrator sets enable-chat=false. To exploit the issue, a SIP MESSAGE must reach a profile that accepts inbound messages. Where authentication is required, access to an account on that profile is enough. SignalWire also notes that the stock vanilla directory includes users without a password or A1 hash. Unless allow-empty-password is set to false for those users, they may authenticate without separate credentials.

The CVSS rating of “no privileges required” doesn’t mean every instance is reachable regardless of network configuration. Teams should verify both their software versions and whether inbound SIP MESSAGE traffic can reach each profile. SignalWire warns that FreeSWITCH inbound ACLs do not cover MESSAGE traffic, meaning those ACLs alone will not protect an otherwise reachable profile.

Where things stand: Patching and mitigations

FreeSWITCH 1.11.3 fixes CVE-2026-116779. The release introduces an enable-chat-api-proto setting to control whether inbound messages can select the api chat protocol. The setting is off by default, closing this route unless an administrator explicitly enables it. Organizations should upgrade to 1.11.3 or later and verify that the updated service build is running in production. If patching right away isn’t feasible, SignalWire recommends setting enable-chat=false on every profile that doesn’t need inbound SIP chat. This disables inbound MESSAGE handling on those profiles, so check for legitimate messaging use before applying the workaround.

Partial defenses can lower risk, but they don’t fully fix the issue. Enforcing message authentication and removing directory users without password material can reduce unauthenticated access, but SignalWire notes that authenticated accounts can still exploit the flaw. Similarly, disabling system API commands is insufficient because other registered APIs remain available. Since FreeSWITCH inbound ACLs don’t cover MESSAGE traffic, adjusting those ACL rules alone won’t secure the vulnerable route.

How Bitsight can help

Bitsight External Attack Surface Management helps security teams spot internet-facing assets and evaluate exposure across internal environments and third-party vendors. Dynamic Vulnerability Exploit (DVE) scores supply threat context, helping teams prioritize vulnerabilities with evidence of exploitation and heightened threat actor interest.

For CVE-2026-116779, external visibility can help surface FreeSWITCH instances that need review. An external scan alone cannot verify the exact build, profile options, or whether a SIP MESSAGE is accepted. Teams should validate these details with asset owners, review system logs and configuration, and confirm patch levels on each host.

Wrapping up

CVE-2026-116779 transforms a crafted SIP MESSAGE into a path for executing FreeSWITCH API commands. Because inbound chat is enabled by default in stock profiles, organizations shouldn’t assume only custom setups are at risk. SignalWire says exploitation has been observed in the wild, and CISA’s KEV listing adds urgency to remediation. Upgrade to FreeSWITCH 1.11.3 or later. In the interim, apply the enable-chat=false workaround to profiles that do not require inbound chat.

CVE-2026-116779: What to do next

  • Inventory FreeSWITCH instances across your environment and identify those running version 1.11.2 or earlier.
  • Upgrade affected systems to FreeSWITCH 1.11.3 or later, then verify the patched service build is active in production.
  • If upgrading immediately isn’t possible, set enable-chat=false on profiles that don’t need inbound SIP chat.
  • Audit profile exposure, SIP MESSAGE authentication settings, directory users without password material, enabled modules, and the operating-system permissions assigned to the service.
  • Check SIP and FreeSWITCH logs for suspicious inbound MESSAGE activity or unusual API calls, and investigate anomalies as potential compromises.
Bitsight cta background color
2026 gartner magic quadrant cover

Bitsight Recognized as a Visionary in 2026 Gartner® Magic Quadrant™ for Cyber Threat Intelligence Technologies

Get the report and see why Bitsight was named a Visionary.

 

Download

Bitsight cta background color