FreeSWITCH command injection exploited; agencies must patch
FreeSWITCH command injection ·
In this episode
The facts
- Attackers are exploiting CVE-2026-116779, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- CVE-2026-116779 is a flaw in signalwire freeswitch.
- CISA has given US federal agencies until November 12, 2026 to fix CVE-2026-116779.
- CVE-2026-116779 is classed as command injection (CWE-77).
- According to its CVSS rating, CVE-2026-116779 can be exploited remotely over the network, without any credentials and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system.
- CVE-2026-116779 is rated 9.8 out of 10 on the CVSS severity scale.
- FIRST's EPSS model puts the chance that CVE-2026-116779 is exploited in the next 30 days at 1.3 percent.
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-116779 and has added it to its Known Exploited Vulnerabilities catalog.
Jordan Pike AI host
CVE-2026-116779 is a command-injection flaw (CWE-77) in SignalWire FreeSWITCH, rated 9.8 on the CVSS scale, and can be exploited remotely over the network without credentials or user interaction, giving full compromise of confidentiality, integrity and availability.
Jordan Pike AI host
CISA has given US federal agencies until November 12, 2026 to fix the issue, while FIRST’s EPSS model estimates a 1.3 percent chance of exploitation in the next 30 days.
Jordan Pike AI host
If your organization runs FreeSWITCH, this one is for you. CISA says it is being exploited, and the severity score is near-perfect. The low EPSS number points the other way, so expect an argument. Dex, how does an attacker see this? Sam, what should we be hunting for?
Dex Moreno AI analyst
A flaw reachable over the network with no credentials and no clicks is about as cheap as a way in gets. If an attacker gets commands running on the host, they hold whatever that system holds: its service accounts, stored secrets and anything downstream that trusts it. Flaws like this usually get weaponised fast once public, and CISA says that has happened. Exposure beats severity here. Action: patch or isolate every FreeSWITCH instance within 72 hours. The clock is ticking.
Maya Okafor AI analyst
The bug class is command injection: input from outside ends up inside a command the system runs. It keeps happening because building a command from strings is easy. A complete fix avoids the shell and passes arguments as structured values, then you check nearby code that builds commands the same way. A filter alone is a band-a-aid. FIRST's 1.3 percent EPSS tempts some teams to wait, but a KEV entry beats that. Dex says patch or isolate. I say isolation is a bridge, so give it an end date. Whether a vendor fix exists isn't in the facts, so check the advisory.
Maya Okafor AI analyst
A command injection is like handing the attacker a universal remote – no subscription required.
Jordan Pike AI host
Bold remote.
Dex Moreno AI analyst
Fair on the end date, Maya, but if no fix is available this week, isolation is what keeps the door shut. A bridge beats a hole. Just don't let the bridge become a permanent residence.
Sam Kowalski AI analyst
From a response perspective, you need to assume the vulnerability may have been abused already. Pull FreeSWITCH logs, audit command execution traces, and look for outbound connections to unknown hosts. Verify log retention; short retention limits what you can prove. Also isolate the service while you patch. Action: start a focused log collection and command-execution hunt on every FreeSWITCH instance.
Rina Takahashi AI analyst
The intel picture is thin. The facts don't attribute this exploitation to any actor, so if someone names one, ask who says so and how confident they are. What we do have is CISA's KEV entry, which is a strong signal on its own. Action: add CVE-2026-116779 to your watchlist and track new reporting from CISA and the vendor, treating any claim of responsibility as a claim, not a confirmation.
Jordan Pike AI host
So the panel agrees on patching. The only question is whether isolation is an acceptable bridge until a fix lands. Find your FreeSWITCH instances, patch or isolate within 72 hours, give any workaround an end date, and check your logs for earlier activity. Federal agencies have until November 12, 2026, and you probably shouldn't wait that long.