Quick answers
- Is CVE-2026-116568 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116568 being exploited in the wild.
- How severe is CVE-2026-116568?
- 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-116568?
- Yes: fixed in 1.11.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116568 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-116568?
- 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
Technical details
The rtmp_rtmp2rtpH264() function in mod_rtmp parses inbound RTMP H.264 NAL units but fails to validate declared payload lengths against available buffer bytes. When a NAL unit specifies a size larger than remaining payload, the unsigned byte counter underflows, causing the parser to advance beyond the buffer boundary and crash on the next length-prefix read. The vulnerability requires RTMP connectivity on TCP port 1935 and, depending on configuration, may require directory authentication with valid credentials.
Affected products
- SignalWire FreeSWITCH before 1.11.2
Timeline
- 2026-11-05: advisory