← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-116779 exploited? Yes: in CISA KEV since 9 Nov 2026

Gociux · SignalWire FreeSwitch · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-116779, SignalWire FreeSwitch Code Injection Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 9 Nov 2026, 4 days after it was published. It affects SignalWire FreeSwitch. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 9 Nov 2026
ransomwareNot knownno confirmed use
EPSSbelow top 10%lower predicted activity right now (it is still confirmed exploited)
severity9.8CVSS 3.1 · critical
US federal due12 Nov 2026BOD 22-01 deadline

What it is

SignalWire FreeSwitch contains a code injection vulnerability that permits configuration and credential disclosure, arbitrary call control, and command execution.

VendorSignalWire (1 exploited CVE in KEV)
ProductFreeSwitch
VulnerabilitySignalWire FreeSwitch Code Injection Vulnerability
WeaknessCWE-77, CWE-78, CWE-749
Published5 Nov 2026
Added to KEV9 Nov 2026
Reported by (CNA)GitHub_M

What to do

  1. Check whether you run it. Look for FreeSwitch in your asset inventory, including appliances and cloud images. Stack check lists every exploited SignalWire CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 5 Nov 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for SignalWire.

References

Questions

Is CVE-2026-116779 being exploited?

Yes. CISA added CVE-2026-116779 to the Known Exploited Vulnerabilities catalog on 9 Nov 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-116779 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2026-116779?

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. Check SignalWire's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected FreeSwitch and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in November 2026 · act-now radar.

Running SignalWire in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →