<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VulnFeed.org: signalwire freeswitch</title><link>https://vulnfeed.org/</link><description>Every disclosure, as it lands. Critical-only feed available.</description><language>en</language><atom:link href="https://vulnfeed.org/feed/product/signalwire-freeswitch.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-116782: FreeSWITCH: Pre-authentication invalid pointer dereference in mod_rtmp connect command handling</title><link>https://vulnfeed.org/cve/CVE-2026-116782/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116782/</guid><pubDate>Thu, 05 Nov 2026 20:17:45 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, rtmp_i_connect() passed the first RTMP connect argument to amf0_object_get() without checking whether the AMF value was an object. A string or number in place of an AMF object caused union bytes from the message to be interpreted as node pointers and dereferenced. Any client with network access to an enabled mod_rtmp listener could send the malformed connect command before login; the module is disabled in the stock build and configuration. The invalid read reliably crashes FreeSWITCH and ends every active call, while no write, memory disclosure, or code execution has been demonstrated. This issue is fixed in version 1.11.2.</description></item><item><title>CVE-2026-116784: FreeSWITCH: Out-of-bounds read in RTCP NACK feedback parsing</title><link>https://vulnfeed.org/cve/CVE-2026-116784/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116784/</guid><pubDate>Thu, 05 Nov 2026 20:17:45 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, process_rtcp_report() used an RTPFB NACK packet&apos;s declared RTCP header length as its feedback-entry loop bound instead of the datagram length already validated by the caller. A short packet with an oversized declaration could drive reads far beyond the fixed 16 KiB receive buffer. Any peer able to send RTCP to an active video call can reach the flaw, including calls where remote SDP enables video RTCP even though the SIP profile has no explicit RTCP interval configured. The out-of-bounds read can crash FreeSWITCH and terminate every active call, but supplies no write primitive and does not echo the read values to the sender. This issue is fixed in version 1.11.2.</description></item><item><title>CVE-2026-116569: FreeSWITCH: Pre-authentication out-of-bounds write in MSRP message body parsing</title><link>https://vulnfeed.org/cve/CVE-2026-116569/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116569/</guid><pubDate>Thu, 05 Nov 2026 20:17:44 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, msrp_parse_buffer() subtracted delimiter framing from a peer-controlled short segment whose MSRP byte range ended in * without first proving the segment was long enough. The unsigned result wrapped near SIZE_MAX and reached switch_msrp_msg_set_payload() as both an allocation size and memcpy length, while related pointer arithmetic could read before the receive buffer. The listener is disabled by default in msrp.conf.xml, but any deployment enabling an MSRP TCP or TLS port parses this framing before authentication. An unauthenticated network peer can corrupt memory and crash FreeSWITCH, dropping all active calls, although remote code execution has not been demonstrated. This issue is fixed in version 1.11.2.</description></item><item><title>CVE-2026-116570: FreeSWITCH: Pre-authentication stack buffer overflow in mod_xml_rpc HTTP directory authentication</title><link>https://vulnfeed.org/cve/CVE-2026-116570/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116570/</guid><pubDate>Thu, 05 Nov 2026 20:17:44 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, http_directory_auth() rebuilt an expected user@domain:password credential and base64-encoded it into an 80-byte buffer using an encoder without an output-length argument. A configured credential longer than 57 characters overflowed the stack before the supplied HTTP Basic password was compared. An unauthenticated client only needed to name an existing directory user on an exposed mod_xml_rpc HTTP listener; the module is built but not loaded by the stock configuration. The overflow can corrupt the stack and crash FreeSWITCH, ending every active call, although the overrun bytes come from the configured credential and remote code execution has not been demonstrated. This issue is fixed in version 1.11.2.</description></item><item><title>CVE-2026-116779: FreeSWITCH: Inbound SIP MESSAGE can select the api chat proto and run FreeSWITCH API commands</title><link>https://vulnfeed.org/cve/CVE-2026-116779/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116779/</guid><pubDate>Thu, 05 Nov 2026 20:17:44 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.3, sofia_presence_handle_sip_i_message() split the To user of an inbound SIP MESSAGE on a plus sign and treated the left side as a chat protocol selector. Selecting the api chat proto reached switch_api_execute(), allowing a peer whose MESSAGE was accepted to run FreeSWITCH API commands, including operating-system command sinks, with the daemon&apos;s privileges. Inbound chat is enabled on the stock internal and external profiles, and any authenticated profile account is sufficient; stock directory users without password material can also remove that barrier in affected configurations. The flaw permits configuration and credential disclosure, arbitrary call control, and command execution, and exploitation has been observed in the wild. This issue is fixed in version 1.11.3.</description></item><item><title>CVE-2026-116567: FreeSWITCH: Pre-authentication stack buffer overflow in mod_rtmp control-message handling</title><link>https://vulnfeed.org/cve/CVE-2026-116567/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116567/</guid><pubDate>Thu, 05 Nov 2026 20:17:43 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, rtmp_handle_control() rendered an RTMP user-control message into a 200-byte stack buffer using an unbounded sprintf loop controlled by the wire message length. A body of roughly 70 bytes or more overflowed the stack before any RTMP login, because the handshake authenticates neither side. The flaw affects deployments that build and load mod_rtmp, which is disabled in the stock build and configuration but commonly exposes a listener on TCP port 1935 when enabled. One unauthenticated message can crash FreeSWITCH and end every active call; the constrained ASCII hex output has not yielded control-flow hijacking. This issue is fixed in version 1.11.2.</description></item><item><title>CVE-2026-116568: FreeSWITCH: Out-of-bounds read in mod_rtmp H.264 video message parsing</title><link>https://vulnfeed.org/cve/CVE-2026-116568/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116568/</guid><pubDate>Thu, 05 Nov 2026 20:17:43 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, rtmp_rtmp2rtpH264() trusted the length prefix of each inbound H.264 NAL unit without checking it against the bytes remaining in the RTMP message. An oversized declared unit underflowed the unsigned remaining-byte counter and advanced the parser beyond its receive buffer, where the next length-prefix read could crash the process. The flaw affects deployments that build and load mod_rtmp and accept video call sessions, commonly on TCP port 1935; placing the call requires a directory login where auth-calls is true, while no credentials are required where auth-calls is absent or false. A remote client can terminate FreeSWITCH and every active call, but the defect supplies no write primitive and memory disclosure has not been demonstrated. This issue is fixed in version 1.11.2.</description></item><item><title>CVE-2026-116783: FreeSWITCH mod_spandsp: out-of-bounds write parsing UDPTL error-recovery data</title><link>https://vulnfeed.org/cve/CVE-2026-116783/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116783/</guid><pubDate>Thu, 05 Nov 2026 19:41:44 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, udptl_rx_packet() used a peer-controlled FEC entry count directly to fill five-entry FEC arrays in a mod_spandsp T.38 session. A larger count wrote sender-controlled error-recovery data beyond those arrays and persisted the oversized count for a later reconstruction pass. Any peer able to deliver UDPTL to an established T.38 fax session can reach the parser, including deployments using fax applications or a T.38 gateway. The memory corruption can crash FreeSWITCH and end every active call, although remote code execution has not been demonstrated. This issue is fixed in version 1.11.2.</description></item><item><title>CVE-2026-116790: FreeSWITCH: Inbound ICE connectivity checks are accepted without verifying STUN MESSAGE-INTEGRITY</title><link>https://vulnfeed.org/cve/CVE-2026-116790/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116790/</guid><pubDate>Thu, 05 Nov 2026 19:40:51 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, FreeSWITCH&apos;s inbound ICE handling accepted every connectivity check without cryptographically validating its STUN MESSAGE-INTEGRITY attribute. A network peer able to reach an ICE-enabled leg&apos;s media port could forge an ICE connectivity check without SDP credentials, nominate its own address, redirect RTP and DTLS traffic, and terminate the legitimate media path. On unencrypted legs this enables eavesdropping and media injection, while all WebRTC and SIP legs that negotiate ICE are in scope. Version 1.11.2 introduces the remediation, which requires ice_verify_message_integrity=true.</description></item><item><title>CVE-2026-116788: FreeSWITCH: Pre-authentication heap buffer overflow in core XML empty-entity decoding</title><link>https://vulnfeed.org/cve/CVE-2026-116788/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116788/</guid><pubDate>Thu, 05 Nov 2026 19:39:44 +0000</pubDate><description>FreeSWITCH is an open-source software telecommunications platform. Before version 1.11.2, an integer underflow in switch_xml_decode() can cause an undersized heap allocation when an XML document declares an entity with an empty replacement value. Subsequent copying overruns the allocated buffer. An unauthenticated attacker who can reach a SIP profile with presence management enabled and DTD processing permitted can trigger the vulnerability through a crafted SIP PUBLISH request. Exploitation can corrupt heap memory and terminate the FreeSWITCH process, interrupting all active calls. This vulnerability is fixed in version 1.11.2.</description></item><item><title>CVE-2026-116789: FreeSWITCH: DTLS-SRTP peer certificate is not bound to the SDP fingerprint when FreeSWITCH is the DTLS server</title><link>https://vulnfeed.org/cve/CVE-2026-116789/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116789/</guid><pubDate>Thu, 05 Nov 2026 19:29:17 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, dtls_state_setup() compared a peer certificate with the SDP a=fingerprint only when FreeSWITCH was the DTLS client, not when it held the DTLS server role. An unauthenticated peer able to reach the negotiated media port could complete the DTLS-SRTP handshake with an unrelated certificate, obtain the leg&apos;s SRTP keys, decrypt and inject media, and displace the legitimate endpoint; on ICE-enabled legs the peer also needs the connectivity-check credentials from SDP, which generally requires signaling visibility or a position on its path. WebRTC and SIP DTLS-SRTP legs are affected whenever the peer selects the active role, while FreeSWITCH client-role handshakes already perform fingerprint validation. Version 1.11.2 introduces the remediation, which requires rtp_dtls_client_cert_verify_mode=fingerprint.</description></item><item><title>CVE-2026-116785: FreeSWITCH: Pre-authentication heap out-of-bounds write in mod_xml_rpc WebSocket frame length handling</title><link>https://vulnfeed.org/cve/CVE-2026-116785/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116785/</guid><pubDate>Thu, 05 Nov 2026 19:26:13 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, ws_read_frame() decoded a WebSocket frame&apos;s 64-bit extended payload length with a 32-bit byte swap and narrowed the result into a signed length. A value whose surviving low word became negative bypassed the signed size check and was reinterpreted as an enormous unsigned count, causing client bytes to overwrite memory beyond the 64 KiB receive buffer. Any client completing a /socket WebSocket upgrade on an enabled mod_xml_rpc endpoint reached the parser before HTTP authentication; both the module and WebSocket endpoint are disabled by default. The heap overwrite can corrupt connection pointers and crash FreeSWITCH, ending every concurrent session, although remote code execution has not been demonstrated. This issue is fixed in version 1.11.2.</description></item><item><title>CVE-2026-116786: FreeSWITCH: Channel-variable injection via SIP REFER leads to command execution in mod_sofia</title><link>https://vulnfeed.org/cve/CVE-2026-116786/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116786/</guid><pubDate>Thu, 05 Nov 2026 19:25:23 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, sofia_handle_sip_i_refer() placed raw Refer-To URI parameters and headers inside a sip_invite_params channel-variable block passed to switch_ivr_originate(). The originate parser treated a comma in the attacker-controlled value as a variable separator, allowing an authenticated caller on a bridged call to inject arbitrary variables into a newly originated leg. An injected execute_on_originate value could invoke the system dialplan application before answer and execute operating-system commands with the FreeSWITCH process privileges. SIP REFER is enabled by default, and the sender needs only a registered account and a call that takes the off-box transfer path, not administrative or Event Socket access. This issue is fixed in version 1.11.2.</description></item><item><title>CVE-2026-116787: FreeSWITCH: Pre-authentication process termination in the Event Socket via an unbounded Content-Length</title><link>https://vulnfeed.org/cve/CVE-2026-116787/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-116787/</guid><pubDate>Thu, 05 Nov 2026 19:24:15 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, mod_event_socket used an unauthenticated Content-Length value directly as the allocation size for an Event Socket message body. Negative or extremely large values could overflow the terminator calculation or force an allocation failure through a helper that aborts the FreeSWITCH process. The header is parsed before the Event Socket password, so any host admitted by apply-inbound-acl can trigger termination with its first packet; the default loopback ACL limits ordinary installations to local clients. The outbound socket dialplan path is also affected when FreeSWITCH connects to a hostile application server, and process termination drops every active call until the service is restarted. This issue is fixed in version 1.11.2.</description></item><item><title>CVE-2026-115928: FreeSWITCH: Stack buffer overflow parsing the SDP a=crypto key material on inbound calls</title><link>https://vulnfeed.org/cve/CVE-2026-115928/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-115928/</guid><pubDate>Thu, 05 Nov 2026 19:15:12 +0000</pubDate><description>FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, switch_core_media_add_crypto() passed the encoded key and salt length from an inbound SDP a=crypto attribute to switch_b64_decode() as the destination capacity. A zero-length key and salt made that capacity underflow, allowing the decoded attribute to overflow a fixed stack buffer with sender-chosen bytes before the call was answered. On the shipped external profile, an unauthenticated caller can reach the SDES-SRTP parser, while profiles that challenge inbound calls remain affected for senders who can authenticate; setting rtp_secure_media_inbound to false removes the path, and WebRTC DTLS-SRTP legs are unaffected. The overflow corrupts memory and can crash the FreeSWITCH process, dropping every active call, although remote code execution has not been demonstrated. This issue is fixed in version 1.11.2.</description></item></channel></rss>
