FreeSWITCH: Inbound SIP MESSAGE can select the api chat proto and run FreeSWITCH API commands
Any FreeSWITCH SIP profile that accepts inbound MESSAGE is exposed by default, since chat handling is on unless a profile sets enable-chat=false. Fixed in 1.11.3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- Fixed in 1.11.3
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 54/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
FreeSWITCH, a software telecom switching stack, has a flaw in how it handles inbound SIP MESSAGE requests that lets a remote attacker, without logging in, run FreeSWITCH API commands, including operating-system commands, with the daemon's privileges. An attacker can use this to disclose configuration and credentials, control calls, and execute commands, and public exploit code is available.
Read the original 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.
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub · Unknown: No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 9.8
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 1.11.3.
Workaround: Set enable-chat=false on every profile that does not need inbound SIP chat.
Timeline
- CVE published
- First seen by cve.now
- Exploit code on GitHub
majidrahimi5020-lgtm/Poc-exploit-for-CVE-2026-116779-FreeSWITCH-
- Posted on X by cve.now
Affected versions
- signalwire freeswitch
fixed in 1.11.3
Evidence 5
- Advisory
- Exploit
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116779
Is CVE-2026-116779 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data
What does this mean?
An inbound SIP MESSAGE can select the api chat protocol and run FreeSWITCH API commands. Those commands run with the privileges of the FreeSWITCH process, which allows arbitrary OS commands, disclosure of configuration and credentials, and full call control.Source: github.com
Which versions are affected by CVE-2026-116779?
freeswitch: before 1.11.3.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 1.11.3 are affected. The exposure applies to any SIP profile that accepts inbound MESSAGE, because chat handling is on by default unless a profile sets enable-chat=false. To check, confirm your installed FreeSWITCH version and review the enable-chat setting on each SIP profile.Source: github.com
How do I fix CVE-2026-116779?
Upgrade to FreeSWITCH 1.11.3 or later. Until the upgrade is done, set enable-chat=false on every profile that does not need inbound SIP chat.Source: github.com