Quick answers
- Is CVE-2026-57190 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57190 being exploited in the wild.
- How severe is CVE-2026-57190?
- Informational severity, published 27 October 2026.
- Which products and versions are affected?
- Asterisk Project Asterisk before 20.20.1, 21.12.3, 22.10.1, 23.4.1; Asterisk Project Certified Asterisk before 20.7-cert11, 22.8-cert3.
- Is there a fix for CVE-2026-57190?
- Yes: fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1; Certified Asterisk 20.7-cert11, 22.8-cert3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57190 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-57190?
- 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
Technical details
SQL injection vulnerability in cel_pgsql.c and cel_tds.c where the eventtype field is inserted directly into SQL queries without proper escaping or sanitization. While other string fields in these modules correctly use PQescapeStringConn() (PostgreSQL) and anti_injection() (MSSQL), the user_defined_name field bypasses these protections. An attacker with the ability to call CELGenUserEvent in the dialplan can inject arbitrary SQL through this field to read or modify database contents.
Affected products
- Asterisk Project Asterisk before 20.20.1, 21.12.3, 22.10.1, 23.4.1
- Asterisk Project Certified Asterisk before 20.7-cert11, 22.8-cert3
Timeline
- 2026-10-27: disclosed