Quick answers
- Is CVE-2026-115928 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115928 being exploited in the wild.
- How severe is CVE-2026-115928?
- High severity, with a CVSS score of 7.5, published 5 November 2026.
- Which products and versions are affected?
- SignalWire FreeSWITCH before 1.11.2.
- Is there a fix for CVE-2026-115928?
- Yes: fixed in 1.11.2. Until then: Set rtp_secure_media_inbound to false to disable the SDES-SRTP parsing path, or restrict inbound calls to authenticated senders only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115928 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-115928?
- Check whether you run SignalWire FreeSWITCH at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.11.2
Set rtp_secure_media_inbound to false to disable the SDES-SRTP parsing path, or restrict inbound calls to authenticated senders only.
Technical details
The switch_core_media_add_crypto() function in the SDP crypto attribute parser accepts a key-salt length value from an inbound a=crypto attribute and passes it as a buffer capacity to switch_b64_decode(). When the parsed key-salt is zero-length, the capacity underflows, permitting a stack buffer overflow with attacker-controlled decoded bytes. The vulnerability affects the SDES-SRTP path reachable by unauthenticated callers on default external profiles; callers who authenticate, or systems using WebRTC DTLS-SRTP, are unaffected. Memory corruption causes process crash and call dropping; RCE is not demonstrated.
Affected products
- SignalWire FreeSWITCH before 1.11.2
Timeline
- 2026-11-05: advisory: CVE-2026-115928 published