SignalWire FreeSWITCH · Exploitation reported

FreeSWITCH exploitation observed in the wild; public PoC, fix in 1.11.3

· 1 min read

CVE-2026-116779 lets an authenticated peer run FreeSWITCH API commands, including operating-system commands, with a single SIP MESSAGE; versions prior to 1.11.3 are affected and 1.11.3 fixes it. The PTDBugs registry reports exploitation observed in the wild, and a public PoC (SIP2Shell) is on GitHub. Update to 1.11.3 and restrict SIP profile exposure.

Illustration: FreeSWITCH exploitation observed in the wild; public PoC, fix in 1.11.3
WhatsApp LinkedIn X
HighVulnerabilityExploitation reportedPatched

In 30 seconds

Alleged

The decisive update came today, November 16: the PTDBugs vulnerability registry published entry PT-2026-132064 stating that CVE-2026-116779, a flaw in SignalWire's FreeSWITCH telephony server, has been exploited in the wild. In plain terms, a peer whose SIP MESSAGE is accepted by the server can run FreeSWITCH API commands, the administrative console commands that control the switch, including sinks that execute operating system commands, all with the daemon's privileges. Versions before 1.11.3 are affected, and the registry says 1.11.3 fixes the issue.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

Observed

What turns this from advisory into emergency is that working exploit code is public. A proof of concept named SIP2Shell sits on GitHub, and a day earlier it was making the rounds on Reddit under the tagline that one SIP message means game over for an unpatched server. If you run FreeSWITCH below 1.11.3, patch first and ask questions later.github.comgithub.com · rssOpen original sourceSee in source listSIP2Shell - CVE-2026-116779reddit.com · Anonymous_Wajeeh · r/pwnhub · redditOpen original sourceSee in source listSIP2Shell - CVE-2026-116779i.redd.it · rssOpen original sourceSee in source list

What happened

Alleged

Start with the latest frame. On November 16 the PTDBugs account posted on X that a PoC and exploit have been discovered for CVE-2026-116779, and its registry entry PT-2026-132064 spells out the detail: vendor SignalWire, product FreeSWITCH, versions prior to 1.11.3 affected, command execution among the impacts, exploitation observed in the wild, fix in 1.11.3. Every one of those points is the registry's claim, so far unduplicated by independent evidence in this batch.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

Observed

Now rewind to the origin. On November 15, Reddit user Anonymous_Wajeeh posted SIP2Shell to r/pwnhub, a hacking news community, with the line 'One SIP message = GameOver for unpatched FreeSwitch' and a link to the GitHub exploit, alongside a promo image. That thread is the earliest artifact in this evidence batch.SIP2Shell - CVE-2026-116779reddit.com · Anonymous_Wajeeh · r/pwnhub · redditOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source listSIP2Shell - CVE-2026-116779i.redd.it · rssOpen original sourceSee in source list

Observed

A second exploit artifact also surfaces in the batch on November 16: the achilles-heel repository on GitHub hosts a folder dedicated to CVE-2026-116779. That makes at least two separate public codebases for this bug.github.comgithub.com · rssOpen original sourceSee in source list

Why it matters

Alleged

The registry's impact list is short and ugly: configuration and credential disclosure, arbitrary call control, and command execution. Translated, an attacker could read the switch's config files and the secrets inside them, decide how calls get routed, and run commands on the operating system underneath, all as the FreeSWITCH daemon.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Alleged

Entry requirements are low. Inbound chat is enabled on the stock internal and external profiles, any authenticated profile account is enough to get a MESSAGE accepted, and in affected configurations stock directory users without password material can strip away even that barrier, according to the registry.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Inferred

Stack the public exploit on top and the practical risks write themselves: toll fraud, intercepted or redirected calls, and a foothold on a server that sits inside the voice network. That chain is our inference from the advisory's impact list, not something PTDBugs spelled out.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source list

What to do

Alleged

Update to FreeSWITCH 1.11.3. The registry states the issue is fixed in that version, which means every older deployment should be treated as exposed to this bug.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

Inferred

While you patch, shrink the target. Restrict which SIP profiles are reachable from untrusted networks, since inbound chat is on by default in the stock internal and external profiles. Require real credentials on every profile account and audit the directory for users configured without password material. Then hunt for signs of abuse: unexpected chat traffic reaching the API, unfamiliar API executions in logs, and strange processes on the host. These are defensive steps inferred from the registry's description of how the bug is reached, not a published vendor playbook.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Confirmed and still uncertain

Observed

What the evidence establishes: two public exploit codebases exist, SIP2Shell and the achilles-heel CVE folder; the PTDBugs registry entry PT-2026-132064 describes the flaw, the affected versions, and the fix; and the story traveled through Reddit, GitHub, and X between November 15 and 16.github.comgithub.com · rssOpen original sourceSee in source listSIP2Shell - CVE-2026-116779reddit.com · Anonymous_Wajeeh · r/pwnhub · redditOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Inferred

What remains open: the claim of exploitation in the wild comes from the registry alone, with no victim, telemetry, or incident detail in the batch. Who wrote SIP2Shell and why, whether in the wild activity predates or follows the public PoC, how many deployments are exposed, and whether SignalWire has published its own advisory are all unanswered here.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source list

What people are saying

Observed

PTDBugs on X, matter of fact: 'A PoC/exploit has been discovered for vulnerability CVE-2026-116779.' The post then carries the full technical description and links to the database entry.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Observed

Reddit's Anonymous_Wajeeh went for the blunt version: 'One SIP message = GameOver for unpatched FreeSwitch.' It is hype shaped language, but the registry's own description says a single accepted MESSAGE can indeed reach operating system command execution, so the boast is not far off the documented mechanics.SIP2Shell - CVE-2026-116779reddit.com · Anonymous_Wajeeh · r/pwnhub · redditOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Evolution

Inferred

The picture shifted twice in two days. On November 15 the evidence was a Reddit post plus a GitHub repo, a flashy exploit with no advisory around it. On November 16 the PTDBugs registry supplied the frame: a CVE number, affected versions, a fix, and the claim that exploitation is already happening. In evidence terms the story moved from weapon available to weapon available and allegedly in use.SIP2Shell - CVE-2026-116779reddit.com · Anonymous_Wajeeh · r/pwnhub · redditOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Inferred

Attention is still climbing rather than settling: a second exploit repo surfaced in the batch the same day the advisory landed, which usually means more researchers and more attackers are pulling on the same thread.github.comgithub.com · rssOpen original sourceSee in source listptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Reach

Observed

4 independent groups, 2 updates, and 0 engagements. Observed communities: r/pwnhub.

Technical detail

Alleged

The mechanics, as the registry describes them: in versions before 1.11.3, the function sofia_presence_handle_sip_i_message() splits the To user of an inbound SIP MESSAGE at a plus sign and treats the left side as a chat protocol selector. Selecting the api chat protocol routes the message into switch_api_execute(), the routine that runs FreeSWITCH API commands. Because some of those commands are operating system command sinks, one accepted MESSAGE can end in shell execution with the daemon's privileges.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

Alleged

Reachability is the multiplier. Inbound chat is enabled on the stock internal and external profiles, any authenticated profile account is sufficient for a MESSAGE to be accepted, and stock directory users without password material can also remove that authentication barrier in affected configurations.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source list

Sources and evidence

Observed

Primary records: the PTDBugs registry entry PT-2026-132064 and the PTDBugs post on X, both from November 16. The X post carries the fullest description of the flaw, impact, and fix, and it anchors nearly every technical claim in this story.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

Observed

Exploit and community artifacts: the SIP2Shell repository and the achilles-heel repository's CVE-2026-116779 folder on GitHub, plus the November 15 Reddit post and its image promoting SIP2Shell. The only other item in the batch is an automated subreddit welcome comment with no evidential value.github.comgithub.com · rssOpen original sourceSee in source listgithub.comgithub.com · rssOpen original sourceSee in source listSIP2Shell - CVE-2026-116779reddit.com · Anonymous_Wajeeh · r/pwnhub · redditOpen original sourceSee in source list

Inferred

Read with care: the registry and GitHub items arrived without readable bodies in this batch, the technical description survives only through the PTDBugs post, and there is no vendor advisory from SignalWire, no patch diff, and no incident data. Every claim of real world exploitation currently rests on a single source.ptdbugsx.com · ptdbugs · xOpen original sourceSee in source listdbu.gsdbu.gs · rssOpen original sourceSee in source list

Sources

  1. ptdbugsx.com · ptdbugs · x
  2. dbu.gsdbu.gs · rss
  3. github.comgithub.com · rss
  4. SIP2Shell - CVE-2026-116779reddit.com · Anonymous_Wajeeh · r/pwnhub · reddit
  5. SIP2Shell - CVE-2026-116779i.redd.it · rss
  6. github.comgithub.com · rss

Incidents like this, every morning

The ones that need action first, in a 3-minute read.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Get the next one tomorrow morning

One email a day with what changed, what to fix first and how.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Share it with your team

Whoever handles security with you should get it too.

LinkedIn X

Your colleague gets a confirmation request. Nothing is sent unless they confirm.

See all news

Read also

Before you go: get this every day

The HIFY Radar daily edition lands every morning with the incidents that need action. Free.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click