Quick answers
- Is CVE-2026-57185 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57185 being exploited in the wild.
- How severe is CVE-2026-57185?
- Medium severity, with a CVSS score of 6.5, 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; Asterisk Project Certified Asterisk before 20.7-cert11, 22.8-cert3.
- Is there a fix for CVE-2026-57185?
- Yes: fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1; Certified Asterisk 20.7-cert11, 22.8-cert3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57185 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-57185?
- Check whether you run Asterisk Project Asterisk or Asterisk Project Certified 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
Technical details
A buffer over-read vulnerability exists in the PJSIP MWI (Message Waiting Indicator) body parser in res/res_pjsip_pubsub.c. An authenticated attacker can trigger the crash by sending a malformed SIP NOTIFY request with Content-Type: application/simple-message-summary. The fix adds length validation to prevent reading past buffer boundaries.
Affected products
- Asterisk Project Asterisk before 20.20.1, 21.12.3, 22.10.1, 23.4.1
- Asterisk Project Certified Asterisk before 20.7-cert11, 22.8-cert3
Timeline
- 2026-10-27: disclosed