CVE-2026-116779
CVE-2026-116779 is a security flaw in SignalWire FreeSwitch. Attackers can run their own code on SignalWire FreeSwitch. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 9 Nov 2026.[1]
SignalWire FreeSwitch is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. SignalWire has published a fix or advice.
Description
CISA calls it a code injection in SignalWire FreeSwitch. In its words: “SignalWire FreeSwitch contains a code injection vulnerability that permits configuration and credential disclosure, arbitrary call control, and command execution.”[1]
The CVE record adds: “FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.3, sofia_presence_handle_sip_i_message() split the To user of an inbound SIP MESSAGE on a plus sign and treated the left side as a chat protocol selector. Selecting the api chat proto reached switch_api_execute(), allowing a peer whose MESSAGE was accepted to run FreeSWITCH API commands, including operating-system command sinks, with the daemon's privileges. Inbound chat is enabled on the stock internal and external profiles, and any authenticated profile account is sufficient; stock directory users without password material can also remove that barrier in affected configurations. The flaw permits configuration and credential disclosure, arbitrary call control, and command…”[2]
The underlying weakness is command injection (CWE-77), OS command injection (CWE-78), CWE-749, in MITRE’s list of common software weaknesses.
It scores 9.8 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by the organisation that published the CVE using CVSS 3.1.[2]
Affected versions
NVD’s record doesn’t list version ranges for it; SignalWire’s advisory has them[3]. CISA names the product as SignalWire FreeSwitch.
Most families won’t have SignalWire FreeSwitch; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 9 Nov 2026, 4 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 12 Nov 2026 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 22%. That’s in the top 3% of the flaws it scores.[4]
CISA assesses it as automatable: attackers can run it against many targets at once.
CISA doesn’t say who was attacked, or how.
Fix
SignalWire has published a fix or advice.[3] CISA’s required action: “Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes).”[1]
- Check whether you use it.SignalWire FreeSwitch is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 12 Nov 2026 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 9.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at 22%.[4] |
See also
Other command injection flaws
- CVE-2026-105134, AhsayCBS: command injection ·
- CVE-2026-96951, Microsoft Windows: command injection ·
- CVE-2016-3081, Apache Struts: command injection ·
- CVE-2026-8037, Progress LoadMaster: command injection ·
- CVE-2025-29635, D-Link DIR-823X: command injection ·
Added the same day
- CVE-2026-123218, IBM Aspera Faspex: incorrect authorization ·
- CVE-2026-123158, OpenBSD OpenSSH: unexpected status code or return value ·
- CVE-2026-102895, GPUStack: improper authentication ·
References
- ^ Cybersecurity and Infrastructure Security Agency. “SignalWire FreeSwitch Code Injection Vulnerability”. Known Exploited Vulnerabilities Catalog, added 9 Nov 2026.
- ^ National Institute of Standards and Technology. “CVE-2026-116779 Detail”. National Vulnerability Database, published 5 Nov 2026.
- ^ SignalWire. Advisories and fixes: github.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.221, percentile 97.7, 19 Nov 2026.
- CVE Program. “CVE-2026-116779”. The official CVE record.
This article is built from CISA’s catalog (version 2026.11.18), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.

