Is CVE-2026-116779 exploited in the wild?

Yes. CVE-2026-116779 is known to be exploited in the wild, first recorded on 9 November 2026. Treat it as urgent.

How severe is CVE-2026-116779?

Critical severity, with a CVSS score of 9.8, published 5 November 2026.

Which products and versions are affected?

SignalWire FreeSWITCH before 1.11.3.

How is CVE-2026-116779 attacked?

It is attacked over the network.

Am I affected by CVE-2026-116779?

Check whether you run SignalWire FreeSWITCH at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-116779: FreeSWITCH command injection via SIP MESSAGE chat protocol

CVE-2026-116779 · Severity: critical · CVSS 9.8 · Exploited in the wild · Published 2026-11-05

FreeSWITCH is a telecommunications platform that routes and processes phone calls over IP networks. A flaw in SIP MESSAGE handling allowed attackers to select a chat protocol that executes arbitrary FreeSWITCH API commands with daemon privileges, potentially leading to system compromise, credential theft, and unauthorized call control. The vulnerability requires an authenticated profile account or a stock configuration user, and has been observed in active exploitation.

Technologies: SignalWire FreeSWITCH. Vendors: SignalWire.

Quick answers

Is CVE-2026-116779 exploited in the wild?: Yes. CVE-2026-116779 is known to be exploited in the wild, first recorded on 9 November 2026. Treat it as urgent.
How severe is CVE-2026-116779?: Critical severity, with a CVSS score of 9.8, published 5 November 2026.
Which products and versions are affected?: SignalWire FreeSWITCH before 1.11.3.
Is there a fix for CVE-2026-116779?: Yes: fixed in 1.11.3. Until then: Disable the api chat protocol selector on affected profiles by setting enable-chat-api-proto to false or omitting it from configuration, which is the default state in the fixed version. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-116779 attacked?: It is attacked over the network.
Am I affected by CVE-2026-116779?: Check whether you run SignalWire FreeSWITCH at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 1.11.3

Disable the api chat protocol selector on affected profiles by setting enable-chat-api-proto to false or omitting it from configuration, which is the default state in the fixed version.

Technical details

FreeSWITCH's sofia_presence_handle_sip_i_message() function parsed the To user field of inbound SIP MESSAGE frames, splitting on a plus sign to select a chat protocol handler. Selecting the "api" proto routed the message directly to switch_api_execute(), bypassing intended restrictions. This affects all authenticated SIP profiles where inbound chat is enabled (default on internal and external profiles), with exploitation requiring only basic SIP authentication.

Affected products

SignalWire FreeSWITCH before 1.11.3

Timeline

2026: exploited: Exploitation observed in the wild prior to advisory
2026-11-05: disclosed
2026-08-26: patched: Fix merged as pull request #3135

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.