Skip to content
Log inRegister

FreeSWITCH CVE-2026-116779: One SIP MESSAGE Can Run Commands, Exploited and in CISA KEV

Dr. Abeer Alshammari · Published 11/10/2026

IntermediateProfessionalsCISOsExecutives

Bottom line: FreeSWITCH servers up to version 1.11.2 can be made to run operating system commands by a single crafted SIP MESSAGE. Exploitation in the wild is reported and the flaw is listed in CISA KEV. Upgrade to 1.11.3 and review SIP logs.

What happened

CVE-2026-116779 affects SignalWire FreeSWITCH, widely used to build telephony, conferencing and contact centre systems. When a SIP MESSAGE is addressed to a user whose name begins with api+, the server treats the text before the plus sign as a chat protocol selector and passes the remainder to its internal API executor, with no check on which protocol the sender picked. That makes it possible to run the system command as the FreeSWITCH process. Where mod_lua is loaded, a second execution route exists. The flaw is scored CVSS 9.8. A GitHub advisory and technical write-ups report exploitation in the wild, and coverage of CISA's 9 November additions lists it in KEV. I could not open the CISA alert page, so the KEV listing and the federal deadline come from secondary coverage.

Why it matters

Voice servers are often internet-facing by design, run with broad privileges, and sit beside call recordings, customer data and trunk credentials. They are also frequently managed by telecom teams rather than the central security function, so patch cycles can lag.

Who is affected

Organisations and service providers running FreeSWITCH 1.11.2 or earlier, including cloud telephony, call centres and PBX deployments. Exposure is highest where SIP chat is enabled on a profile and either authentication is weak or the stock passwordless default user remains. Where authentication is enforced, a single valid account is enough.

Technical impact

Successful exploitation gives command execution with the privileges of the FreeSWITCH service. That can lead to theft of SIP and trunk credentials, toll fraud, access to call recordings and a foothold for movement into the internal network.

Governance impact

Telephony platforms rarely appear in vulnerability management scope or in third-party risk reviews, yet they process personal data and can generate direct financial loss through fraud. KEV listing also gives regulators and auditors a clear marker that the risk was publicly known.

What security teams should do

Upgrade to FreeSWITCH 1.11.3 or later, which adds an enable-chat-api-proto setting that is off by default, and rebuild any custom packages that include the affected modules. If you cannot upgrade at once, set enable-chat to false on every profile that does not need SIP chat, remove directory users that have no password, and keep SIP signalling reachable only from trusted peers. Search logs for MESSAGE requests containing api+. If a successful request cannot be ruled out, treat the host as compromised, rebuild it and rotate SIP and trunk credentials.

What executives should know

Ask who owns your telephony stack and whether it is on the patch programme. A compromised voice server can mean fraud costs and exposed customer calls, so the question is operational and financial as well as technical.

Sources checked: Ostorlab technical analysis of CVE-2026-116779, the nflo.tech knowledge base entry, and securityonline.info coverage of the CISA KEV additions of 9 November 2026. The CISA alert page could not be opened, so the KEV listing and federal deadline are reported from secondary coverage. Summarised in my own words; confirm versions with the vendor release notes before acting.

Try it yourself

An interactive CyberAbeer experience for this topic is in development.

Coming soon
Back to insights