Answer in brief
CVE-2026-57201 records a High severity (CVSS 7.5) vulnerability in Asterisk: Stack Buffer Overflow in H.323 ooTrace() via Unbounded vsprintf into Fixed 2048-byte Buffer. The current sources do not mark it as known exploited. The current feed maps asterisk/asterisk (generic), asterisk/certified-asterisk (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps asterisk/asterisk (generic), asterisk/certified-asterisk (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| asterisk/asteriskgeneric | <20.20.1 || >=21.0.0-pre1 <21.12.3 || >=22.0.0-pre1 <22.10.1 || >=23.0.0-pre1 <23.4.1 | 20.20.1, 21.12.3, 22.10.1, 23.4.1 |
| asterisk/certified-asteriskgeneric | <20.7-cert11 || >=22.8-cert1-pre1 <22.8-cert3 | 20.7-cert11, 22.8-cert3 |
Published upstream
Oct 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 27, 2026
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.
Quoted source text, attributed separately from HOL analysis.