SignalWire FreeSwitch: attackers can run their own code
OFFICIAL NAME: SignalWire FreeSwitch Code Injection Vulnerability
DO THIS FIRSTFind out if you use it. If you do, apply the vendor's fix. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY SignalWire FreeSwitch contains a code injection vulnerability that permits configuration and credential disclosure, arbitrary call control, and command execution.
WHY THIS VERDICT Attacks are confirmed. The vulnerability is 5 days old, so many systems are likely still unpatched. The severity score is critical (9.8).
WHY IT RANKS HERE Exploitation is confirmed by an authoritative source. The confirmation is 2 days old.
- HIGHEST CONFIRMED RUNG
- EXPLOITED
- CISA KEV
- LISTED
- EXPLOIT CODE
- PROOF OF CONCEPT CLAIMED
How far has it climbed?
01 TALK
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESCVE-2026-116779 discussed publicly (CIRCL sighting). CVE-2026-116779 discussed publicly (CIRCL sighting).
02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESAttacks that worked are confirmed (step 4), so attempts count as confirmed too.
04 EXPLOITED
■ CONFIRMEDNEWEST EVIDENCE · 2 INDEPENDENT SOURCESCISA Vulnrichment marks CVE-2026-116779 as actively exploited. SignalWire FreeSwitch contains a code injection vulnerability that permits configuration and credential disclosure, arbitrary call control, and command execution.
05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLICCLAIMED
- FIRST ATTACK REPORT
- CISA KEV LISTING
- US FEDERAL DEADLINE
THE FIX
CISA's instruction: apply the vendor's fix, or stop using the product if no fix exists. CISA set Nov 12, 2026 as the deadline for US federal agencies. It is a US government deadline; use it as a guide.
Questions to ask this week
- Do we run SignalWire FreeSwitch? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- NOV 1, 20262 public GitHub repositories claim a proof of concept for CVE-2026-116779
- Attack activity. NOV 8, 2026SignalWire FreeSwitch Code Injection Vulnerability
- Attack activity. NOV 9, 2026CISA Vulnrichment marks CVE-2026-116779 as actively exploited
- NOV 9, 2026CVE-2026-116779 discussed publicly (CIRCL sighting) (30 reports, latest NOV 10)
- NOV 10, 2026IBM Aspera Faspex, SignalWire FreeSwitch Vulnerabilities Exploited in Attacks
SOURCES
- [1] CIRCL Vulnerability-Lookup sightings: CVE-2026-116779 discussed publicly (CIRCL sighting), NOV 10
- [2] SecurityWeek: IBM Aspera Faspex, SignalWire FreeSwitch Vulnerabilities Exploited in Attacks, NOV 10
- [3] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment marks CVE-2026-116779 as actively exploited, NOV 9
- [4] CISA Known Exploited Vulnerabilities: SignalWire FreeSwitch Code Injection Vulnerability, NOV 8
- [5] PoC-in-GitHub: 2 public GitHub repositories claim a proof of concept for CVE-2026-116779, NOV 1
- [6] CIRCL Vulnerability-Lookup sightings: 29 more reports