Is CVE-2026-57192 exploited in the wild?

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

How severe is CVE-2026-57192?

Informational severity, published 27 October 2026.

Which products and versions are affected?

Asterisk Project Asterisk prior to 20.20.1, 21.12.3, 22.10.1, 23.4.1; Asterisk Project Certified Asterisk prior to 20.7-cert11, 22.8-cert3.

How is CVE-2026-57192 attacked?

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

Am I affected by CVE-2026-57192?

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-57192: Asterisk heap buffer overflow in Codec2 decoder

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

Asterisk is an open-source phone system and telecommunications toolkit used to manage voice, video, and messaging communications. An authenticated attacker who can establish a call using Codec2 audio compression can trigger a heap buffer overflow by sending specially crafted audio packets, potentially causing a crash or code execution. This requires the Codec2 module to be loaded and the attacker to pass SIP authentication.

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

Quick answers

Is CVE-2026-57192 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57192 being exploited in the wild.
How severe is CVE-2026-57192?: Informational severity, published 27 October 2026.
Which products and versions are affected?: Asterisk Project Asterisk prior to 20.20.1, 21.12.3, 22.10.1, 23.4.1; Asterisk Project Certified Asterisk prior to 20.7-cert11, 22.8-cert3.
Is there a fix for CVE-2026-57192?: 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 codec_codec2 module if Codec2 is not required, or restrict SIP access to trusted IP addresses to limit authentication bypass vectors. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57192 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-57192?: 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

Disable the codec_codec2 module if Codec2 is not required, or restrict SIP access to trusted IP addresses to limit authentication bypass vectors.

Technical details

A floor/ceiling mismatch in the Codec2 decoder causes an out-of-bounds write: the codec2_samples() function uses floor division to compute output buffer space, but the decode loop uses a condition that allows one extra iteration with ceiling behavior when the input length is not a multiple of CODEC2_FRAME_LEN. The fix changes the loop condition from (x < datalen) to (x + CODEC2_FRAME_LEN <= datalen) to process only complete frames. Attack requires SIP authentication (username/password or source IP) and an established call.

Affected products

Asterisk Project Asterisk prior to 20.20.1, 21.12.3, 22.10.1, 23.4.1
Asterisk Project Certified Asterisk prior to 20.7-cert11, 22.8-cert3

Timeline

2026-10-27: disclosed: CVE-2026-57192 published
2026: patched: Fix released in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3

References

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