VulnerabilityPublished 5 Nov 2026

CVE-2026-116784: signalwire freeswitch · Out-of-bounds Read

Affects signalwire freeswitchSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.11.2 soon.

Data as of 5 Nov 2026, 19:52 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	7.5

Patch: Available – fixed in 1.11.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade signalwire freeswitch to 1.11.2.

Affected software

Product	Affected	Fixed in
signalwirefreeswitch	Affected <1.11.2	Fixed in 1.11.2

AI-suggested

Upgrade FreeSWITCH to version 1.11.2 or later, where this vulnerability is fixed. No other mitigation is required as the issue is resolved in the official patch.

Description

CVE-2026-116784 is an out-of-bounds read vulnerability in FreeSWITCH prior to version 1.11.2. The flaw occurs in the process_rtcp_report() function when handling RTPFB NACK packets with an incorrectly declared RTCP header length, which can cause reads beyond the allocated buffer. This can lead to a crash of FreeSWITCH and termination of all active calls. The vulnerability does not allow writing or leaking data back to the attacker. It is fixed in FreeSWITCH version 1.11.2.

Impact

Exploitation of this vulnerability can cause FreeSWITCH to crash, resulting in denial of service by terminating all active calls. There is no impact on confidentiality or integrity as the flaw does not provide a write primitive or leak read data back to the attacker.

Summary

FreeSWITCH versions prior to 1.11.2 contain a CWE-125 out-of-bounds read vulnerability in the process_rtcp_report() function. The function uses the RTCP header length declared in an RTPFB NACK packet as the loop bound for feedback entries instead of the datagram length validated by the caller. If a short packet declares an oversized length, this can cause reads beyond the fixed 16 KiB receive buffer. Any peer sending RTCP to an active video call can trigger this, including calls with remote SDP enabling video RTCP without explicit RTCP interval configuration in the SIP profile. The out-of-bounds read can crash FreeSWITCH and terminate all active calls. The issue is fixed in version 1.11.2.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 19:52 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats