Quick answers
- Is CVE-2026-57199 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57199 being exploited in the wild.
- How severe is CVE-2026-57199?
- Informational severity, published 27 October 2026.
- Which products and versions are affected?
- Asterisk Project Asterisk before 20.20.1, 21.12.3, 22.10.1, 23.4.1.
- Is there a fix for CVE-2026-57199?
- Yes: fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1; Certified Asterisk 20.7-cert11, 22.8-cert3. Until then: Disable the SMS dialplan application if not in use, or ensure all SMS input is validated before being passed to the SMS application. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57199 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-57199?
- Check whether you run Asterisk Project Asterisk 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: Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1; Certified Asterisk 20.7-cert11, 22.8-cert3
Disable the SMS dialplan application if not in use, or ensure all SMS input is validated before being passed to the SMS application.
Technical details
A buffer overflow exists in app_sms.c where protocol 1 SMS unpacking functions copy externally controlled SMS lengths into fixed-size buffers without bounds checking, allowing memory corruption of adjacent state. The vulnerability requires that the administrator explicitly configures the SMS dialplan application and does not validate incoming SMS data; remote attackers can send malformed SMS messages via the network. The fix adds bounds checking to clamp address, header, and body copies to destination array sizes.
Affected products
- Asterisk Project Asterisk before 20.20.1, 21.12.3, 22.10.1, 23.4.1
Timeline
- 2026-10-27: disclosed