CVE-2026-115928 · Runtime
NO FIX YET · SEE WHAT TO DO
FreeSWITCH before 1.11.2 mishandles the length of an SDP a=crypto key and salt, so a zero-length value underflows a buffer and overflows a fixed stack buffer during call setup. An attacker can crash the process and drop every active call; remote code execution has not been demonstrated.
first public Oct 26, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Operators running FreeSWITCH before 1.11.2 that accept SDES-SRTP calls. On the shipped external profile an unauthenticated caller can reach the vulnerable parser; profiles that challenge inbound calls remain affected for senders who can authenticate. Deployments with rtp_secure_media_inbound set to false and WebRTC-only media are not on this path.
Not affected if rtp-secure-media-disabled, version-1.11.2-or-later, webrtc-only
Who cares freeswitch, self-hosted, telephony, voip
fs_cli -x version or the installed package version.rtp_secure_media_inbound is enabled in the external profile configuration.1.11.2.rtp_secure_media_inbound to false, which removes the affected path (WebRTC DTLS-SRTP legs are unaffected).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.
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.