Quick answers
- Is CVE-2026-49842 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49842 being exploited in the wild.
- How severe is CVE-2026-49842?
- High severity, with a CVSS score of 7.5, published 9 June 2026.
- Which products and versions are affected?
- SignalWire FreeSWITCH < 1.11.1.
- Is there a fix for CVE-2026-49842?
- A patch was published on 2026-05-26: Version 1.11.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49842 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-49842?
- 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.
Technical details
A vulnerability exists in the mod_verto module's WebSocket frame loop where speed-test protocol commands (#SPU, #SPB, #SPE) are processed before authentication. The payload size in the #SPU command is parsed using atoi() without upper-bound validation, allowing an unauthenticated peer to request up to INT_MAX bytes. The server responds by writing approximately 10 times the requested size back to the client, potentially generating 20 GB of outbound traffic from a single small request. This results in significant bandwidth amplification and resource exhaustion. The issue is fixed in version 1.11.1 by requiring authentication for speed-test commands and capping the maximum size to 10 MiB.
Affected products
- SignalWire FreeSWITCH < 1.11.1
Timeline
- 2026-05-26: patched: Version 1.11.1 released
- 2026-06-03: advisory: GitHub Security Advisory published
- 2026-06-09: disclosed: CVE published to NVD