skulldc

CISA lists FreeSWITCH SIP MESSAGE command execution CVE-2026-116779 as exploited

A chat protocol selector in inbound SIP MESSAGE handling let FreeSWITCH peers run API commands, including operating-system commands; fixed in 1.11.3 and listed by CISA as exploited.

What CISA added

On 2026-11-09 CISA added CVE-2026-116779 to its catalog of known exploited vulnerabilities (KEV). The entry is named “SignalWire FreeSwitch Code Injection Vulnerability”, lists SignalWire as the vendor and FreeSwitch as the product, and classifies the weakness as CWE-77, CWE-78 and CWE-749. Known ransomware campaign use is listed as Unknown. For US federal civilian agencies bound by BOD 22-01, the due date is 2026-11-12, a short window.

The KEV notes add that the vulnerability affects an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. In other words, the exposure is not limited to standalone FreeSWITCH servers.

How the bug works

The NVD record, published on 2026-11-05 and in the status Analyzed, describes the bug in detail. In versions prior to 1.11.3, the function sofia_presence_handle_sip_i_message() took the To user of an inbound SIP MESSAGE, split it on a plus sign, and treated the left side as a chat protocol selector. Selecting the api chat proto reached switch_api_execute(). As a result, a peer whose MESSAGE was accepted could run FreeSWITCH API commands, including operating-system command sinks, with the daemon’s privileges.

The path from text message to command execution is short because chat routing and the API dispatcher meet in one place. A field meant to address a chat recipient ended up choosing which internal handler received the message body.

Who can reach it matters. According to NVD, 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 the record states that exploitation has been observed in the wild.

Severity

NVD carries a secondary CVSS 3.1 base score of 9.8 CRITICAL from the GitHub security advisory, with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H: network attack vector, low complexity, no privileges, no user interaction, and high impact on confidentiality, integrity and availability. The PR:N rating sits alongside the description’s mention of an authenticated profile account, which is consistent with the note that directory users without password material can remove that barrier.

What to do

The issue is fixed in version 1.11.3. The NVD references list the fix commit 7015f6a73ab3d67fed5fbfc277ecfb88a74c2a86, pull request 3135, the v1.11.3 release tag, and the advisory GHSA-mg63-h38w-8p9p in the signalwire/freeswitch repository.

The KEV required action is to apply mitigations in accordance with vendor instructions, following CISA’s BOD 26-04 guidance on prioritizing security updates based on risk and its “Forensics Triage Requirements”, or to discontinue use of the product if mitigations are unavailable. Stakeholders are asked to evaluate each asset’s internet exposure.

Operators should upgrade to 1.11.3. Until that is done, it is worth checking whether inbound chat needs to be enabled on the internal and external profiles, and whether any directory users lack password material. Because the flaw allows configuration and credential disclosure, systems that may already have been reached should have the credentials in their configuration rotated. Vendors of products that embed FreeSWITCH are the ones to ask about fixed builds.


Source: CVE-2026-116779 (NVD, CISA KEV)