CVE-2026-116789
FreeSWITCH: DTLS-SRTP peer certificate is not bound to the SDP fingerprint when FreeSWITCH is the DTLS server
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'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.
Fixes and workarounds
Fix
FreeSWITCH (c): GitHub reports patched versions >= 1.11.2. Check the advisory for the affected release branch.
Source: GitHub GHSA-8ghv-ccjr-4cx9Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| freeswitch signalwire |
< 1.11.2 (affected) | CNA: GitHub_M |
FreeSWITCHFreeSWITCH
c |
<= 1.11.1 (affected, GitHub advisory range) | GitHub GHSA-8ghv-ccjr-4cx9 |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 7.4 high |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA: GitHub_M |
| 3.1 / 7.4 high |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | NVD: [email protected] |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/signalwire/freeswitch/security/advisories/GHSA-8ghv-ccjr-4cx9CNA: GitHub_M · x_refsource_CONFIRM
- https://github.com/signalwire/freeswitch/commit/ea74c0acb8b85c5fc50158cd592a1b80c4edf6a6CNA: GitHub_M · x_refsource_MISC
- https://github.com/signalwire/freeswitch/releases/tag/v1.11.2CNA: GitHub_M · x_refsource_MISC
- https://github.com/signalwire/freeswitch/commit/ea74c0acb8b85c5fc50158cd592a1b80c4edf6a6[email protected]
- https://github.com/signalwire/freeswitch/releases/tag/v1.11.2[email protected]
- https://github.com/signalwire/freeswitch/security/advisories/GHSA-8ghv-ccjr-4cx9[email protected]
- https://github.com/signalwire/freeswitch/security/advisories/GHSA-8ghv-ccjr-4cx9GitHub Security Advisories · advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.