On this page (7 sections)
CVE-2026-116779 is a critical code injection flaw in FreeSWITCH, a software defined telecom stack. NVD lists the product as SignalWire FreeSwitch (the vendor name comes from the CISA KEV entry). The CVE description says a peer whose inbound SIP MESSAGE is accepted can run FreeSWITCH API commands, including operating-system command sinks, with the privileges of the FreeSWITCH daemon.
The same description states that exploitation has been observed in the wild, and the CVE is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 2026-11-09. If you run FreeSWITCH, treat this as an urgent upgrade to 1.11.3.
What happened
According to the CVE description, the function sofia_presence_handle_sip_i_message() handles inbound SIP MESSAGE requests. Before 1.11.3, it split the user part of the To address on a plus sign and treated the left side as a chat protocol selector. Selecting the api chat protocol reached switch_api_execute(), so a message meant to carry chat text could run FreeSWITCH API commands.
The description says the impact includes configuration and credential disclosure, arbitrary call control and command execution. Because some API commands are described as operating-system command sinks, the end result can be command execution with the privileges of the user running the FreeSWITCH daemon.
Why it is serious
Three details from the CVE record make this more than a theoretical risk:
- Inbound chat is enabled on the stock internal and external profiles.
- Any authenticated profile account is sufficient. The description adds that stock directory users without password material can also remove that barrier in affected configurations.
- Exploitation is described as observed in the wild, and the CISA KEV entry carries a due date of 2026-11-12.
In plain terms, this is a command injection weakness: part of a SIP address, which the sender controls, decides which internal handler runs. Since the description says any authenticated profile account is enough, you should not count on SIP authentication alone as protection.
Who is affected
According to the CVE record, FreeSWITCH versions prior to 1.11.3 are affected. As a general matter, exposure is likely highest for:
- Servers where the internal or external SIP profiles are reachable from the internet or other untrusted networks.
- Systems with authenticated profile accounts that are weakly protected, or with stock directory users that lack password material in affected configurations.
- Servers where the FreeSWITCH service runs with broad privileges, because commands run with the daemon's rights.
If FreeSWITCH is embedded in a larger product or hosted platform you use, ask your provider which FreeSWITCH version it ships.
How to check your exposure
Start by finding the installed version. This command prints the FreeSWITCH version (run it on the server and look for a version lower than 1.11.3):
freeswitch -versionIf FreeSWITCH came from a package, you can also query the package manager. The package name depends on where you installed it from, so the pattern below is a loose match. Look at the version column in the output:
dpkg -l | grep -i freeswitchrpm -qa | grep -i freeswitchThen check which sockets the service is listening on, to see whether it is reachable beyond where it should be (look for FreeSWITCH sockets bound to public addresses):
ss -lntup | grep -i freeswitchWhat to do now
- Upgrade FreeSWITCH to 1.11.3 or later, the fixed version named in the CVE record. The CVE record lists these references: the v1.11.3 release, a GitHub security advisory, pull request 3135 and a commit.
- If you cannot upgrade today, restrict SIP access with a firewall so only known carriers, trunks and office or VPN addresses can reach the SIP profiles.
- Audit directory users. Remove accounts you do not use and make sure every account has a strong, unique password.
- Review your SIP, API and system logs for activity from unknown sources, such as unexpected MESSAGE requests or API calls you did not make. The research does not describe how exploitation appears in logs, so treat any review as best effort.
- Check for signs of compromise: unexpected processes owned by the FreeSWITCH user, new cron jobs, new SSH keys, changed dialplan or configuration files, and unusual outbound calls or traffic.
- Rotate credentials that FreeSWITCH can read, including SIP account passwords, gateway and trunk credentials, and any API or database secrets in its configuration, since the flaw is described as permitting credential disclosure.
- Run the service as an unprivileged user with limited filesystem access so a future flaw has less reach.
Optional log review
As a rough starting point, this read-only command lists MESSAGE lines containing a plus sign in a FreeSWITCH log. The log location and format are unverified here: the path below is only a common example, your install may log elsewhere, and SIP message headers may not be logged at all at your log level. A hit is not proof of attack, and no hits does not mean the system was not attacked.
grep -i 'MESSAGE' /var/log/freeswitch/freeswitch.log | grep '+'Detection and monitoring afterwards
If the server was exposed before patching, assume that credentials may have been read and plan for a compromise review, not just a version bump. Keep an eye on call detail records for spikes in outbound or premium-rate calls, and on configuration files for unexpected changes.
For the web-facing systems around your telephony stack, regular outside-in checks help you notice changes early. Webforta Monitor can watch uptime, certificates and DNS for your domains, and the free SSL checker is a quick way to verify certificates on any provisioning or web endpoints. These do not inspect SIP traffic or fix this flaw. If you suspect a break-in, follow website hacked: what to do.
Timeline
| Date | Event |
|---|---|
| 2026-11-05 | CVE-2026-116779 published |
| 2026-11-09 | Added to the CISA KEV catalog |
| 2026-11-12 | Due date listed in the CISA KEV entry |
The KEV entry's required action, as quoted in the record, is to apply mitigations in accordance with vendor instructions, following CISA's BOD 26-04 guidance and its Forensics Triage Requirements, or to discontinue use of the product if mitigations are unavailable. The record excerpt is truncated, so check the full entry on CISA's site. As general background, KEV due dates are binding on US federal agencies; other organizations can use the date as a benchmark for urgency.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
