CVE-2026-57190 json
Asterisk: SQL Injection in cel_pgsql and cel_tds via CELGenUserEvent eventtype Field
published 4mo ago modified 14d ago also EUVD-2026-111401 , GHSA-ph27-3m5q-mj5m
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.0
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- 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, 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.
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-57190
- github.com/asterisk/asterisk@046a8b0 commit
- github.com/asterisk/asterisk@0a86e45 commit
- github.com/asterisk/asterisk@88c6575 commit
- github.com/asterisk/asterisk@8bf7746 commit
- github.com/asterisk/asterisk@8cb6dfd commit
- github.com/asterisk/asterisk@a04bee3 commit
- github.com/asterisk/asterisk@ff21d90 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-57190 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-57190 updated cvss 8.1
asterisk: asterisk: Arbitrary SQL execution via CELGenUserEvent dialplan application
-
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
- no
- Technical impact
- partial
- Assessed
- 14d ago
Exploit prediction
0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:H/SI:L/SA:L |
| CNA | 4.0 | 7.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:H/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- asterisk asterisk
- asterisk certified-asterisk
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
- github.com /asterisk/asterisk/commit/046a8b0b50623d80926c1adc2eca1c9c17e258ed
- github.com /asterisk/asterisk/commit/0a86e45e8cde7630276f8363de45f71d1635d2f4
- github.com /asterisk/asterisk/commit/88c65757b56c716b5a175f35941be22e038b256f
- github.com /asterisk/asterisk/commit/8bf7746d01221d6d2bcfcd46ba7a1cff066a1a8b
- github.com /asterisk/asterisk/commit/8cb6dfd41debb2259ec3a33ccfa78f1d902e4c22
- github.com /asterisk/asterisk/commit/a04bee3992c28e1681457370e46f30494b7c6619
- github.com /asterisk/asterisk/commit/ff21d90e61d199db9b963c671d125a1e917d41ac
-
github.com
/asterisk/asterisk/security/advisories/GHSA-ph27-3m5q-mj5m
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-57190
- NVD CVE-2026-57190
- Maintainer advisory GHSA-ph27-3m5q-mj5m
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.