CVE-2026-57201 json
Asterisk: Stack Buffer Overflow in H.323 ooTrace() via Unbounded vsprintf into Fixed 2048-byte Buffer
published 4mo ago modified 12d ago also EUVD-2026-111220 , GHSA-x348-j6c9-77f3
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository asterisk/asterisk. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
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, a stack buffer overflow in the H.323 `ooTrace()` trace-logging function can occur when unbounded `vsprintf` writes into a fixed `2048-byte buffer`. A remote attacker may send a carefully crafted packet that causes the Asterisk process to crash. The `chan_ooh323` addon channel driver must be explicitly compiled and installed, which is not the default, and its port must be publicly reachable. 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.
Patch / fix
- digium certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
- sangoma certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
- digium asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1
- asterisk open_source 20.20.1, 21.12.3, 22.10.1, 23.4.1
- asterisk certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
- asterisk Debian 14 1:22.10.1+dfsg+~cs6.17.60671434-1
debian advisories DEBIAN-CVE-2026-57201
- github.com/asterisk/asterisk@2d7b8c8 commit
- github.com/asterisk/asterisk@33f62e3 commit
- github.com/asterisk/asterisk@875ac74 commit
- github.com/asterisk/asterisk@ac0a64d commit
- github.com/asterisk/asterisk@bf0c9a9 commit
- github.com/asterisk/asterisk@c4d9b4d commit
- github.com/asterisk/asterisk@fff256d commit
- github.com/asterisk/asterisk/releases/tag/20.20.1 release
- github.com/asterisk/asterisk/releases/tag/21.12.3 release
- github.com/asterisk/asterisk/releases/tag/22.10.1 release
Is CVE-2026-57201 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-57201 updated cvss 7.5
asterisk: asterisk: Denial of Service via stack buffer overflow in H.323 trace logging
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 12d ago
Exploit prediction
0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- asterisk asterisk
- asterisk certified-asterisk
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
- github.com /asterisk/asterisk/commit/2d7b8c8dc13d9ead8b6f36cc38b6dd91cd4abd3a
- github.com /asterisk/asterisk/commit/33f62e351642edd9c58ef97b0002132722546af9
- github.com /asterisk/asterisk/commit/875ac7413de0b7068cd12d0da2f140cd06ba9357
- github.com /asterisk/asterisk/commit/ac0a64dec6d4231bf005a68da6af3e02bb311634
- github.com /asterisk/asterisk/commit/bf0c9a906892bc0f91fa753476e326919e4e30e5
- github.com /asterisk/asterisk/commit/c4d9b4defe83f74523880fd630c02c49683786a3
- github.com /asterisk/asterisk/commit/fff256d0539e96f70ac315844d72e9d540f03a4c
-
github.com
/asterisk/asterisk/security/advisories/GHSA-x348-j6c9-77f3
advisory
- github.com /asterisk/asterisk/releases/tag/20.20.1
- github.com /asterisk/asterisk/releases/tag/21.12.3
- github.com /asterisk/asterisk/releases/tag/22.10.1
- github.com /asterisk/asterisk/releases/tag/23.4.1
- github.com /asterisk/asterisk/releases/tag/certified-20.7-cert11
- github.com /asterisk/asterisk/releases/tag/certified-22.8-cert3
- github.com /asterisk/asterisk/tree/24.0.0-pre1
Sources
- CVE List CVE-2026-57201
- NVD CVE-2026-57201
- Maintainer advisory GHSA-x348-j6c9-77f3
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of asterisk/asterisk published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.