Answer in brief
CVE-2026-57190 records a High severity (CVSS 7.0) vulnerability in Asterisk: SQL Injection in cel_pgsql and cel_tds via CELGenUserEvent eventtype Field. 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.0. 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, the `PostgreSQL` and `TDS/MSSQL` Channel Event Log backends `cel_pgsql` and `cel_tds` may permit arbitrary SQL execution when untrusted data is set in the CEL `eventtype` column by the `CELGenUserEvent` dialplan application. The `cel_pgsql` or `cel_tds` backend must be loaded and configured, and the administrator must call `CELGenUserEvent` in the dialplan without ensuring that only valid data is passed to the application. 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.