Is CVE-2026-57187 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-57187 being exploited in the wild.

How severe is CVE-2026-57187?

Informational severity, published 26 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-57187?

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-57187 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-57187?

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.

CVE-2026-57187: Asterisk heap-use-after-free in PJSIP TCP/SDP handling

CVE-2026-57187 · Severity: info · Published 2026-10-26

Asterisk is an open source telephone system and VoIP toolkit used by organizations to manage phone calls and SIP communications. An authenticated attacker can cause the Asterisk service to crash by sending a specially crafted SIP INVITE message over TCP and then disconnecting, potentially disrupting voice communications. The vulnerability only manifests when Asterisk is built with Address Sanitizer, a development tool not typically present in production systems, limiting real-world exploitability.

Technologies: Asterisk Project Asterisk, Asterisk Project Certified Asterisk. Vendors: Asterisk Project.

Quick answers

Is CVE-2026-57187 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57187 being exploited in the wild.
How severe is CVE-2026-57187?: Informational severity, published 26 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-57187?: 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-57187 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-57187?: 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 heap-use-after-free vulnerability exists in the PJSIP message filter component when handling SIP INVITE messages over connection-oriented transports (TCP). The filter_on_tx_message() function incorrectly uses pj_strassign() to assign pointers to transport local addresses instead of copying the actual values; if a connection is closed before the 200 OK response with SDP is transmitted, these pointers become invalid. The vulnerability requires authentication and is actively detected only by Address Sanitizer, a development tool with significant performance overhead not used in production environments.

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-26: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.