CVE Tools

CVE-2026-57190

Asterisk: SQL Injection in cel_pgsql and cel_tds via CELGenUserEvent eventtype Field

No known exploitation. EPSS puts it in the 52nd percentile. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

  • AsteriskAffected: < 20.20.1Upgrade to: not statedAffected: >= 21.0.0-pre1, < 21.12.3Upgrade to: not statedAffected: >= 22.0.0-pre1, < 22.10.1Upgrade to: not statedAffected: >= 23.0.0-pre1, < 23.4.1Upgrade to: not statedStated by: CVE record
  • Asterisk Certified-asteriskAffected: < 20.7-cert11Upgrade to: not statedAffected: >= 22.8-cert1-pre1, < 22.8-cert3Upgrade to: not statedStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS52nd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.7% chance of exploitation activity in the next 30 days, which ranks it in the 52nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 105 days, from the signal feeds we watch.

  1. Record updatedrecord updated
  2. Publishedweakness classified, att&ck mapped, record updated
  3. OpenVAS check added

Affected products

Technical detail

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Asterisk, not every advisory.