Skip to main content
VulnerabilityPublished

CVE-2026-116789: signalwire freeswitch · Improper Certificate Validation

Affects signalwire freeswitchSource CVE Database V5

0
Compare

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

Data as of 5 Nov 2026, 19:51 UTC

CVSS 3.1 base score
7.4High
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.17.4
Patch
Available – fixed in 1.11.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade signalwire freeswitch to 1.11.2.

Affected software

ProductAffectedFixed in
signalwirefreeswitchAffected
  • <1.11.2
Fixed in
  • 1.11.2

AI-suggested

Upgrade FreeSWITCH to version 1.11.2 or later, where the vulnerability is fixed by enforcing DTLS peer certificate validation against the SDP fingerprint for both client and server roles. Specifically, the configuration parameter rtp_dtls_client_cert_verify_mode=fingerprint must be set to require fingerprint verification. No other mitigation is indicated or required as the fix is official and complete.

Description

CVE-2026-116789 is an improper certificate validation vulnerability in SignalWire FreeSWITCH versions prior to 1.11.2. The flaw occurs because FreeSWITCH did not validate the DTLS peer certificate against the SDP fingerprint when acting as a DTLS server, allowing an unauthenticated peer to complete the DTLS-SRTP handshake with an unrelated certificate. This enables the attacker to obtain SRTP keys, decrypt and inject media, and displace the legitimate endpoint. The issue affects WebRTC and SIP DTLS-SRTP legs when the peer selects the active role. Version 1.11.2 fixes this by requiring fingerprint verification via the configuration parameter rtp_dtls_client_cert_verify_mode=fingerprint.

References

Community reviews

Loading reviews…