Exploited CVEs / CVE-2026-116779
CVE-2026-116779
SignalWire FreeSwitch Code Injection Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-11-12 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.
Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.
Actively exploited SignalWire FreeSwitch vulnerability, Critical severity, CVSS v3 9.8. Added to the CISA KEV catalog 2026-11-09.
Updated November 9, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2026-116779
CVE-2026-116779 is a code injection flaw in SignalWire FreeSwitch that lets an attacker disclose configuration and credentials, take control of calls, and run commands on the host. Anyone running FreeSwitch as a PBX, VoIP gateway, or softswitch is exposed, and a successful attack against a telephony server also hands over stored credentials that can be reused elsewhere. Severity is Critical (CVSS 9.8), and CISA added it to the KEV catalog on 2026-11-09 as confirmed exploited, even though the EPSS probability is only 2%, so do not treat the low score as a reason to wait.
Do this: Identify every FreeSwitch instance in your environment, apply the SignalWire fix or mitigation today, and rotate any SIP, ESL, and admin credentials stored on those hosts if they were reachable from untrusted networks.
AI-generated from public data, 2026-11-11. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-116779
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2026-116779
- Published
- 2026-11-09
- Last revised
- 2026-11-09
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
The strongest signal is CISA adding CVE-2026-116779 to its KEV catalog on 2026-11-09, which confirms exploitation in the wild. EPSS began at 1.3% that day, then climbed to 2.2% on 2026-11-10 and 2.5% on 2026-11-13. The steady upward drift supports treating this as a patch-now item rather than waiting for a routine cycle.
Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.
- 2026-11-09 EPSS first scored at 1.3%; added to the CISA KEV catalog by CISA
- 2026-11-10 EPSS 1.3% to 2.2%
- 2026-11-13 EPSS 2.2% to 2.5%
Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.
From the Senserva blog
- One day left for Barracuda, and the clean board lasted a day
November 12, 2026 · Clay, Clay in the Morning - Four flaws, three days: CISA's short-fuse list lands the day before Patch Tuesday reads out
November 10, 2026 · Clay, Clay in the Morning
CISA required action
Federal remediation due date: 2026-11-12 (past due).
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). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Official fix for CVE-2026-116779
Check the vendor's security advisory channel for the patched FreeSwitch versions and workarounds.
Common questions about CVE-2026-116779
Is CVE-2026-116779 actively exploited?
Yes. CVE-2026-116779 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-11-09, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 2.5%.
What is the CISA deadline and required action for CVE-2026-116779?
CISA set the federal remediation due date at 2026-11-12, which has passed; treat any unremediated system as overdue. The verbatim 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). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
What fixes CVE-2026-116779?
Check the vendor's security advisory for the patched FreeSwitch versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2026-116779?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-116779's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).
Scope and sources
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.