CVE-2026-116779 · Runtime
NO FIX YET · SEE WHAT TO DO
FreeSWITCH before 1.11.3 treats the left side of a plus sign in the To user of an inbound SIP MESSAGE as a chat protocol selector, and the api protocol passes the message to the API command executor. An authenticated peer whose message is accepted can run FreeSWITCH API commands, including operating-system command sinks, with the daemon's privileges.
first public Oct 28, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Any FreeSWITCH server before 1.11.3 that accepts inbound SIP MESSAGE traffic is exposed, which includes the stock internal and external profiles. Any authenticated profile account is enough to reach the flaw, and stock directory users without password material can remove that barrier in affected configurations. Systems that have disabled inbound chat or run a patched 1.11.3 or later can skip it.
Not affected if fixed-1.11.3-or-later, inbound-chat-disabled
Who cares freeswitch, self-hosted, sip, telecom
fs_cli -x 'version' or check the installed FreeSWITCH version; affected versions are those before 1.11.3.1.11.3.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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.