Is CVE-2026-57197 exploited in the wild?

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

How severe is CVE-2026-57197?

Informational severity, published 27 October 2026.

Which products and versions are affected?

Asterisk before 20.20.1, before 21.12.3, before 22.10.1, before 23.4.1; Asterisk Certified Asterisk before 20.7-cert11, before 22.8-cert3.

Is there a fix for CVE-2026-57197?

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

It is attacked with local access, in a hosted service.

Am I affected by CVE-2026-57197?

Check whether you run Asterisk or Asterisk 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-57197: Asterisk heap buffer overflow in OGG Speex format handler

CVE-2026-57197 · Severity: info · Published 2026-10-27

Asterisk is an open-source phone system that processes audio files including Speex-encoded OGG formats. A specially crafted corrupted Speex audio file can trigger a heap buffer overflow that crashes Asterisk, disrupting telephony service. An attacker would need to convince an administrator to load a malicious audio file or have sufficient system access to place one where Asterisk will play it.

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

Quick answers

Is CVE-2026-57197 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57197 being exploited in the wild.
How severe is CVE-2026-57197?: Informational severity, published 27 October 2026.
Which products and versions are affected?: Asterisk before 20.20.1, before 21.12.3, before 22.10.1, before 23.4.1; Asterisk Certified Asterisk before 20.7-cert11, before 22.8-cert3.
Is there a fix for CVE-2026-57197?: 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-57197 attacked?: It is attacked with local access, in a hosted service.
Am I affected by CVE-2026-57197?: Check whether you run Asterisk or Asterisk 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

The ogg_speex_read() function in format_ogg_speex.c performs an unbounded memcpy of OGG packet data into a 200-byte buffer without validating packet size, causing a heap buffer overflow when processing corrupted Speex files. This corrupts the adjacent speex_desc structure containing libogg heap pointers, leading to SIGSEGV crash on playback. The attacker must create and deliver the malicious file, requiring either elevated privileges or social engineering of an administrator.

Affected products

Asterisk Asterisk before 20.20.1, before 21.12.3, before 22.10.1, before 23.4.1
Asterisk Certified Asterisk before 20.7-cert11, before 22.8-cert3

Timeline

2026-10-27: disclosed
2026-10-27: patched

References

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