Live › vulnerability › CVE-2026-57197
Go to dashboardA malformed OGG/Speex audio file triggers an unbounded memcpy in Asterisk's format_ogg_speex, overflowing a heap buffer. The result is a crash of the Asterisk process when the file is played.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 17:32 UTC. All times on this page are UTC.
Asterisk deployments older than the fixed releases that are configured to play OGG/Speex files. Exposure depends on whether an attacker can place such a file where Asterisk reads it, which needs elevated privileges or an administrator being tricked into adding it. Systems that do not play Speex files or that only use directories under strict administrator control are less exposed.
No product ranges from the sources yet.
asterisk -V to get the installed version and compare it with the fixed releases.20.20.1, 21.12.3, 22.10.1 or 23.4.1.20.7-cert11 or 22.8-cert3.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Asterisk is an open source private branch exchange and telephony toolkit. Prior to Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3, an unbounded memcpy of OGG/Speex packet data in format_ogg_speex can cause a heap buffer overflow and crash Asterisk when reading a file containing corrupted Speex audio. The attacker must create the file and make it available to Asterisk either through sufficiently elevated privileges or by convincing an Asterisk administrator to make it available. Asterisk must also be configured to play that file. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3.
This page as .md · .json · in your agent: get_signal("CVE-2026-57197")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.