Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-116779: SIP MESSAGE API Command Injection in SignalWire FreeSWITCH

Published Nov 5, 2026 · Updated today
Trending this week#41of 427,679 vulnerabilities
Mention activity · 30 days81 mentions · peak 33 in a dayToday
CVSS9.8Critical · v3.1
EPSS2.5%85th percentile
CISA KEVYesAdded Nov 9, 2026
In the wildActivePer CISA KEV
Vendor
Freeswitch
IdentifiersCVE-2026-116779CWE-77 · Improper Neutralization of Special…

CVE-2026-116779 is a command-injection vulnerability in SignalWire FreeSWITCH versions before 1.11.3. The mod_sofia function sofia_presence_handle_sip_i_message() splits an inbound SIP MESSAGE recipient user field at a plus sign and interprets the prefix as a chat-protocol selector. Selecting the api protocol registered by mod_dptools routes attacker-controlled text to switch_api_execute() without a separate API authorization check. A peer whose MESSAGE is accepted can execute FreeSWITCH API commands, including operating-system command-execution sinks, with the daemon's privileges. Inbound chat is enabled on stock internal and external profiles. Exploitation has been observed in the wild.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises configuration and credential confidentiality, permits arbitrary call control and call origination, and enables module loading and operating-system command execution. Attackers may access recordings and other service-readable data, modify service-writable settings, and disrupt telecommunications services. Available capabilities depend on loaded modules and the FreeSWITCH service account's permissions; exploitation does not inherently confer root privileges.

Mitigation

If you can’t patch tonight, do this now.

Set enable-chat=false on SIP profiles that do not require messaging to stop MESSAGE traffic before vulnerable protocol selection; this also disables legitimate chat. Restrict SIP exposure using network controls, remove or repair passwordless directory users, and explicitly prohibit empty-password authentication. MESSAGE authentication alone does not prevent exploitation by an authorized account, and the inbound SIP ACL does not cover MESSAGE traffic as operators may expect. Setting disable_system_api_commands=true reduces direct operating-system command exposure but leaves other dangerous API capabilities reachable. Least-privilege service accounts, filesystem restrictions, process confinement, and controlled egress can limit impact but do not replace patching.

Remediation

Patch, then assume compromise.

Upgrade to FreeSWITCH 1.11.3 or a supplier-supported build containing the equivalent fix, restart the service, and verify that the running process uses the patched build. Keep enable-chat-api-proto disabled, its patched default; explicitly enabling it reopens API chat dispatch. The fix also restricts inbound MESSAGE destination parsing. Review exposed deployments for prior compromise, including unexpected API activity, module loads, calls, child processes, and persistence. Preserve evidence and replace credentials and keys that may have been exposed.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.

View more in app →
freeswitch-cve-2026-116779-POCThe repository contains a standalone Python exploitation toolkit, an auxiliary Nuclei detection template, packaging metadata, English/Chinese documentation, examples, and an offline test suite. Its 17 files include 10 Python files and one executable YAML template. The fscve console command and python -m fscve expose detect, api, shell, rev, and sweep operations. core.py implements execution and concurrent scanning; sip.py builds MESSAGE requests and MD5/MD5-sess digest authentication; transport.py provides TCP, UDP, and optional SOCKS5; dns.py constructs output-bearing callback hostnames and polls dnslog.cn. The exploit places api+ followed by a percent-encoded command in the SIP To user and request URI. According to the supplied source excerpts, FreeSWITCH routes this to mod_dptools and switch_api_execute(); the system API then provides OS command execution as the daemon. Credentials are used when challenged with 401/407, so anonymous exploitation is configuration-dependent rather than universal. The repository identifies CVE-2026-116779 and claims a fix in 1.11.3, but neither the advisory nor affected-version claims were independently verified from the supplied material. Important limitations: 200/202 only indicates acceptance into asynchronous processing, not execution; a 403 can also reflect policy and does not independently establish a patched version. The DNS builder does not actually truncate output despite its documentation, allowing output to exceed the 63-character DNS-label limit. Custom collector zones require manual observation because StaticZone.wait_for always returns None. The dnslog client does not explicitly preserve session cookies, which may prevent reliable session-based record collection. The detect CLI returns a nonzero exit status even for ACCEPTED because it checks for VULNERABLE, a verdict detect never produces. JSON output uses dictionary union despite declaring Python 3.8 compatibility. The tests exercise encoding, digest authentication, and command delivery to a local UDP mock; the mock does not execute OS commands and does not validate real-target exploitation or DNS callbacks. No obvious operator-directed destructive payload or unrelated malware is present; removal of /tmp/.x is part of the named-pipe reverse shell. Documentation-only IPs and staging paths are examples rather than hardcoded operational infrastructure. The repository URL is inferred from its README; the analyzed Git reference and archive size were not supplied, so the reference is empty and size_bytes is an unknown-value placeholder of 0.hackzuoji · Disclosed Nov 6, 2026 · python · yaml · networkOperationalSIP2ShellThe repository contains a standalone Python exploitation toolkit plus an ancillary Nuclei detector, rather than a primary framework module. Its central mechanism is an attacker-controlled SIP To user beginning with api+, which the documented vulnerable FreeSWITCH chat dispatcher forwards to switch_api_execute(). Selecting the system API yields operating-system command execution as the daemon account. The main entry point, sip2shell.py, exposes scan, probe, exploit, shell, rev, and info commands. Visible code supplies configurable command execution, three reverse-shell presets, SOCKS5 parsing, network defaults, and CLI dispatch. Documentation and tests additionally describe SIP output read-back, an HTTP callback listener, output encoding, digest authentication, retries, and payload-length checks. The runtime is Python 3.8+ using the standard library. No fixed attacker-controlled command-and-control destination is visible. The 18-file structure comprises three Python files, one Bash script, one Nuclei YAML template, CI and Docker Compose YAML, packaging metadata, documentation, licensing, and five SVG illustrations. The five code-bearing files counted here include the executable Nuclei template. lab/ supplies vulnerable 1.10.12 and patched 1.11.3 container configurations using host networking. tests/test_core.py contains 12 unit/smoke tests covering packet construction, parsing, payload constraints, proxy handling, HTTP callbacks, and a simulated SIP exchange. scripts/make_demo.py renders hardcoded captured-session text into a GIF and is not an exploitation component. Important limitations: the supplied main script and README are truncated, so significant implementation details cannot be fully inspected. No code was executed, and the claimed CVE, advisory, exploitation history, KEV status, and live-lab results are not independently verified. SIP 202 means acceptance, not confirmed execution; the visible classifier tests nevertheless label 200/202 vulnerable and 403 patched, which can overstate certainty. The Nuclei template checks response fingerprints rather than command output and declares UDP SIP headers while not explicitly configuring UDP network transport. Root privileges shown in demonstrations are deployment-dependent. The repository reference and archive size were not provided; their fields use an empty string and zero as unknown placeholders.DeathShotXD · Disclosed Nov 14, 2026 · python · bash · networkOperationalCVE-2026-116779The supplied repository contains README.md (3,006 bytes) and a standalone standard-library Python script, exploit.py (8,970 bytes). No exploit framework is used. Repository URL, revision, and archive size were not supplied; empty strings and zero represent unavailable metadata. The README describes a claimed FreeSWITCH flaw in which mod_sofia splits a SIP destination user-part at '+', treats api as the chat protocol, and forwards the remaining text to switch_api_execute(). The script constructs bodyless SIP MESSAGE packets with api+<command> in both the Request-URI and To header, percent-encodes spaces, generates randomized SIP transaction identifiers, sends the packet over IPv4 UDP, and prints one received datagram. It supports single-command execution, a version probe, and a repeated command-entry mode that translates an os: prefix into a system API invocation. Documented consequences include access to SIP configuration and registrations, possible credential disclosure, file reads, and shell-command execution as the daemon account. There are important validation limits. check_target() treats any response containing SIP/2.0 as likely vulnerable, including potential error responses, so it establishes neither command execution nor a vulnerable version. The code does not parse command results, authenticate response senders, or correlate responses with transaction identifiers. It receives only one datagram and has no retransmission, TCP transport, callback listener, or automatic output-exfiltration implementation. The URI builder escapes only spaces; arbitrary shell syntax is not comprehensively URI-encoded. OS stdout is not reliably returned in SIP responses, and the documented reverse-shell and HTTP examples are operator-supplied follow-on commands, not default actions. The claimed Python 3.6+ requirement is inaccurate: evaluated bytes | None and str | None annotations effectively require Python 3.10+. The source docstring also references a different script filename. No hidden downloader, fixed attacker-controlled infrastructure, or unrelated destructive local behavior is evident. This is an operational exploit attempt rather than merely a detector, but static inspection alone cannot verify the claimed CVE, affected releases, patch references, URI-decoding behavior, or successful unauthenticated execution.pentestershell · Disclosed Nov 16, 2026 · python · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreeswitchFreeswitchapplication
FAQ

Frequently asked questions

Is CVE-2026-116779 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 9, 2026.
Is there a public exploit for CVE-2026-116779?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-116779, the earliest disclosed Nov 6, 2026.
Is there a patch for CVE-2026-116779?
Upgrade to FreeSWITCH 1.11.3 or a supplier-supported build containing the equivalent fix, restart the service, and verify that the running process uses the patched build. Keep enable-chat-api-proto disabled, its patched default; explicitly enabling it reopens API chat dispatch.
What products are affected by CVE-2026-116779?
Freeswitch.
How severe is CVE-2026-116779?
CVE-2026-116779 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 2.5% (85th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

81 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
nuclei templates pull requestsNews · Nov 13, 2026CVE-2026-116779 - SignalWire FreeSWITCH < 1.11.3 - SIP MESSAGE api-proto OS Command Injection by DhiyaneshGeek · Pull Request #17813 · projectdiscovery/nuclei-templatesA reported critical OS command-injection vulnerability affecting SignalWire FreeSWITCH versions before 1.11.3 through SIP MESSAGE handling of api-proto destinations. The supplied proof-of-concept attempts command execution, handles SIP digest authentication using default or empty credentials, and demonstrates a DNS callback from a localhost test. This establishes exploit-code availability and controlled testing, not exploitation in the wild. The version boundary suggests a fix, but patch availability is not explicitly confirmed.Read more ↗linuxsecurityNews · Nov 11, 2026FreeSWITCH Exploitation Risks Linux VoIP Servers, Fix in 1.11.3A command-execution vulnerability affecting FreeSWITCH through version 1.11.2 when an incoming SIP MESSAGE can reach the vulnerable handler. A crafted destination selects the api chat protocol, allowing accepted messages to invoke server API commands without a separate API permission check. Potential consequences include configuration and credential disclosure, call manipulation, module loading, and operating-system command execution with the FreeSWITCH service account's privileges. SIP authentication alone does not prevent exploitation by permitted accounts. Version 1.11.3 fixes the flaw; disabling unused SIP chat with enable-chat=false provides a temporary mitigation. CISA confirms exploitation, but the content identifies no victims, malware families, or threat actors.Read more ↗security affairsNews · Nov 10, 2026U.S. CISA adds IBM, SignalWire FreeSwitch, OpenSSH, and GPUStack flaws to its Known Exploited Vulnerabilities catalogA code injection vulnerability affecting SignalWire FreeSWITCH versions before 1.11.3 allows attackers to send crafted SIP MESSAGE requests and abuse the API chat protocol to execute FreeSWITCH API commands. Depending on configuration, exploitation can expose credentials and configuration data, manipulate telephone calls, and execute operating system commands with the FreeSWITCH process's privileges.Read more ↗heiseNews · Nov 10, 2026Angriffswarnung für GPUStack, FreeSwitch, OpenSSH und IBM Aspera Faspex | heise onlineCritical FreeSwitch vulnerability allowing any authenticated account to execute arbitrary code, read credentials, and control calls. The article reports a CVSS score of 9.8 and CISA-confirmed exploitation. Version 1.11.3 and later fix the vulnerability.Read more ↗
+9 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity65Community discussion across Reddit, Mastodon, and other social sources.