TL;DR: Upgrade FreeSWITCH to version 1.11.3 or later immediately; if patching is not immediately possible, follow CISA KEV guidance under BOD 26-04 and restrict inbound SIP MESSAGE processing to trusted peers only.
What Is the Vulnerability?
CVE-2026-116779 is a critical code injection vulnerability (CVSS 3.1 score: 9.8, Severity: CRITICAL) affecting SignalWire FreeSWITCH, an open-source software-defined telecom stack widely used to replace proprietary switching hardware with commodity servers.
The root cause lies in the sofia_presence_handle_sip_i_message() function. When FreeSWITCH receives an inbound SIP MESSAGE, it splits the To header's user portion on a plus (+) character and interprets the left-hand segment as a chat protocol selector. If that selector matches the api chat protocol, execution is handed off to switch_api_execute() — FreeSWITCH's internal API dispatcher.
This design flaw (classified under CWE-77: Improper Neutralization of Special Elements used in a Command, CWE-78: OS Command Injection, and CWE-749: Exposed Dangerous Method or Function) means that a crafted SIP MESSAGE can invoke FreeSWITCH API commands that reach operating-system command sinks, all running with the daemon's own privileges.
The attack vector is network-based, requires no user interaction, and demands no elevated privileges — the CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects full confidentiality, integrity, and availability impact.
Who and What Is Affected?
Any deployment of FreeSWITCH prior to version 1.11.3 is potentially affected. Key exposure factors include:
- Default profiles enabled: Inbound SIP chat is enabled in FreeSWITCH's stock internal and external SIP profiles out of the box, meaning unmodified installations are exposed by default.
- Low authentication bar: Any authenticated profile account is sufficient to trigger the vulnerable code path. According to NVD findings, stock directory users without password material can also remove that authentication barrier in certain affected configurations.
- Broad deployment base: FreeSWITCH is used in hosted PBX platforms, contact centres, telco infrastructure, and CPaaS environments — amplifying the potential blast radius.
Organizations should audit every FreeSWITCH instance regardless of whether it is internet-facing; lateral movement through internal SIP trunks is a realistic secondary risk.
What Is the Impact?
Successful exploitation of CVE-2026-116779 can result in:
- Operating-system command execution at the privilege level of the FreeSWITCH daemon process.
- Configuration and credential disclosure — SIP credentials, dial-plan logic, and system configuration files accessible to the daemon can be exfiltrated.
- Arbitrary call control — an attacker can manipulate active calls, redirect traffic, intercept media, or generate fraudulent calls (toll fraud).
- Full system compromise if the daemon runs with root or elevated OS privileges, as is common in many deployments.
CISA added this CVE to the Known Exploited Vulnerabilities (KEV) catalog on 2026-11-09, confirming that exploitation has been observed in the wild. All three impact dimensions — confidentiality, integrity, and availability — are rated HIGH by NVD.
What Should You Do Right Now?
The following actions are prioritised in line with CISA KEV guidance and the vendor's own advisory:
- Upgrade to FreeSWITCH 1.11.3 or later. Version 1.11.3 is the confirmed fix for this issue, as documented by the vendor and recorded in NVD. This is the primary remediation.
- Apply CISA BOD 26-04 patching timelines. Federal civilian agencies are subject to BOD 26-04 patch deadlines for KEV entries. All organisations should treat this with equivalent urgency given confirmed in-the-wild exploitation.
- Restrict inbound SIP MESSAGE processing. As an interim control, limit which SIP peers are permitted to send inbound chat/MESSAGE requests. Remove or restrict stock internal/external profile access from untrusted network segments.
- Review daemon privilege levels. Ensure FreeSWITCH runs under a dedicated, least-privilege service account rather than root wherever possible.
- Audit stock directory accounts. Review all configured SIP directory users and ensure no accounts lack proper credential enforcement, as noted in the NVD description.
- Conduct forensic triage. Per CISA's KEV required action, perform forensic triage on affected systems to identify any signs of prior compromise before and after patching.
- Discontinue use if mitigations are unavailable. Per CISA guidance, if the patch cannot be applied and effective mitigations cannot be implemented, discontinue use of the affected product.
Primary references: NVD entry for CVE-2026-116779 | CISA KEV Catalog.
How Continuous External Testing Surfaces This Exposure
CVE-2026-116779 is an excellent illustration of why periodic, point-in-time assessments are insufficient for internet-exposed infrastructure. Consider the exposure chain:
- FreeSWITCH instances are frequently deployed on non-standard ports or behind thin SIP proxies, making them easy to miss in manual asset inventories.
- The vulnerability requires only a single crafted SIP MESSAGE from a legitimately authenticated peer — a condition that could be satisfied by any enrolled SIP endpoint or softphone.
- Default profile enablement means newly provisioned or cloned instances inherit the vulnerability silently.
Continuous external attack surface testing addresses each of these gaps by:
- Discovering SIP and RTP endpoints across your routable IP space, including those provisioned after the last manual scan.
- Flagging unpatched FreeSWITCH versions through non-intrusive banner and version-disclosure checks without sending exploitative payloads.
- Alerting on configuration drift — for example, detecting when a stock external SIP profile becomes reachable from the public internet.
- Tracking KEV status automatically, so that the moment a CVE enters the CISA catalog, all asset owners receive prioritised notification rather than waiting for the next scheduled assessment cycle.
The CVSS 9.8 score, combined with confirmed in-the-wild exploitation and CISA KEV listing, places this vulnerability at the absolute top of remediation queues. Organisations with continuous external visibility can correlate patch deployment against live exposure in near-real time.
Sources & further reading: NVD CVE-2026-116779 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: github.com, github.com, github.com, github.com. This advisory contains no exploit code.
Frequently asked questions
Does an attacker need valid SIP credentials to exploit CVE-2026-116779?
According to the NVD description, any authenticated profile account is sufficient to trigger the vulnerability. The description also notes that stock directory users without password material can remove that barrier in certain affected configurations, potentially lowering the authentication requirement further.
Is this vulnerability being actively exploited?
Yes. The NVD description states that exploitation has been observed in the wild, and CISA added CVE-2026-116779 to its Known Exploited Vulnerabilities catalog on 2026-11-09, confirming active exploitation.
What is the fix, and is there a workaround if I cannot patch immediately?
The official fix is upgrading to FreeSWITCH version 1.11.3 or later, as confirmed by the vendor and documented in NVD. If patching is not immediately possible, CISA advises applying available mitigations — such as restricting which SIP peers can send inbound chat/MESSAGE requests and limiting network exposure of affected profiles — and following BOD 26-04 guidance. If no effective mitigations are available, CISA recommends discontinuing use of the product.
Are cloud-hosted FreeSWITCH deployments also affected?
CISA's required action explicitly mentions evaluating each asset's internet exposure and following applicable BOD 26-04 guidance for cloud services. Cloud-hosted instances running FreeSWITCH prior to 1.11.3 with default SIP profiles enabled should be treated as affected and patched or mitigated with the same urgency as on-premises deployments.