CVE-2026-116571: signalwire freeswitch · Stack-based Buffer Overflow
Affects signalwire freeswitchSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 1.11.2 when convenient.
Data as of 5 Nov 2026, 20:03 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 1.11.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade signalwire freeswitch to 1.11.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| signalwirefreeswitch | Affected
| Fixed in
|
AI-suggested
Upgrade FreeSWITCH to version 1.11.2 or later, where this vulnerability is fixed. Since the mod_rtmp module is disabled by default, disabling or not loading this module also mitigates the risk. No other specific mitigations are indicated.
Description
CVE-2026-116571 is a stack-based buffer overflow vulnerability in FreeSWITCH's mod_rtmp module prior to version 1.11.2. The flaw occurs in the rtmp_rtp2rtmpH264() function, which copies SPS and PPS values into a fixed stack buffer without validating their size, allowing an attacker to overflow the stack. This vulnerability affects only deployments that enable mod_rtmp and bridge RTP media into an RTMP leg, which is disabled by default. Exploitation can cause FreeSWITCH to abort and terminate all active calls. While code execution has not been demonstrated, builds lacking stack protection may allow limited stack writes. The issue is fixed in version 1.11.2.