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.
CVE-2026-57190
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (52nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-111401 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.0
- EG Score
- 7.0HIGHmedium confidence
- EG Risk
- 32EG Risk 32/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity70% × 45%Impact severity (EG Severity): CVSS 7.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.7% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.7%
- EPSS %ILE
- 52nd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 27, 2026
Last Modified
October 28, 2026
Advisory Details (10)
Auto-updated Oct 27, 2026Asterisk Release 22.10.1
Patch available: asterisk/asterisk 22.10.1
https://github.com/asterisk/asterisk/releases/tag/22.10.1Asterisk Release 21.12.3
Patch available: asterisk/asterisk 21.12.3
https://github.com/asterisk/asterisk/releases/tag/21.12.3Asterisk Release 20.20.1
Patch available: asterisk/asterisk 20.20.1
https://github.com/asterisk/asterisk/releases/tag/20.20.1commit ff21d90e61d1 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit ff21d90e61d1 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/ff21d90e61d199db9b963c671d125a1e917d41accommit a04bee3992c2 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit a04bee3992c2 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/a04bee3992c28e1681457370e46f30494b7c6619commit 8cb6dfd41deb (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 8cb6dfd41deb — awaiting tagged release
https://github.com/asterisk/asterisk/commit/8cb6dfd41debb2259ec3a33ccfa78f1d902e4c22commit 8bf7746d0122 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 8bf7746d0122 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/8bf7746d01221d6d2bcfcd46ba7a1cff066a1a8bcommit 88c65757b56c (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 88c65757b56c — awaiting tagged release
https://github.com/asterisk/asterisk/commit/88c65757b56c716b5a175f35941be22e038b256fcommit 0a86e45e8cde (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 0a86e45e8cde — awaiting tagged release
https://github.com/asterisk/asterisk/commit/0a86e45e8cde7630276f8363de45f71d1635d2f4commit 046a8b0b5062 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 046a8b0b5062 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/046a8b0b50623d80926c1adc2eca1c9c17e258edWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-28 17:26 UTCEG score recompute
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
- 2026-10-28 16:25 UTCEG score recompute
- 2026-10-27 22:28 UTCEG score recompute
- 2026-10-27 22:01 UTCENISA EUVD ID recordedEUVD-2026-111401 · Source: ENISA EUVD
- 2026-10-27 21:50 UTCEG score recomputeFirst assessed: 7.0 HIGH
- 2026-10-27 21:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-57190?
When was the CVE record for CVE-2026-57190 published?
Is CVE-2026-57190 actively exploited?
What is the CVSS score of CVE-2026-57190?
How do I remediate CVE-2026-57190?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-57190
Is Your Infrastructure Affected by CVE-2026-57190?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.