CVE-2026-116790 · Runtime
NO FIX YET · SEE WHAT TO DO
FreeSWITCH accepted ICE connectivity checks without validating their STUN MESSAGE-INTEGRITY attribute, so a network peer can forge a check without SDP credentials. The forged check redirects RTP and DTLS media, letting an attacker eavesdrop on or inject into unencrypted calls and terminate the legitimate media path on WebRTC and SIP legs that use ICE.
first public Oct 28, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Systems running FreeSWITCH before 1.11.2 that handle WebRTC or SIP calls using ICE and have media ports reachable by a network peer are exposed. Deployments that do not use ICE legs, or that sit behind networks where media ports are not reachable by untrusted peers, are lower risk. The sources do not say how many deployments are reachable.
Not affected if media-ports-not-reachable, no-ice-legs, version-1.11.2-or-later
Who cares freeswitch, sip, telecom, voip, webrtc
fs_cli -x version and compare it to the fixed range.ice_verify_message_integrity in the FreeSWITCH configuration; it is not set to true if the fix is not applied.1.11.2 or later, and set ice_verify_message_integrity=true, per the sources.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'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'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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.