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, an out-of-bounds write in chan_unistim DIALPAGE digit handling can overflow the phone_number field and crash Asterisk when an attacker sends a carefully crafted incoming request packet. The chan_unistim module must be loaded and configured with a valid UNISTIM UDP port that the attacker can reach. The attacker must register as a configured phone MAC, or the deployment must have an equivalent production/autoprovisioning path that allows the client to reach the main page. 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-57194
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-111217 (ENISA EUVD)Source: ENISA EUVD
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.9
- EG Score
- 5.9MEDIUMmedium confidence
- EG Risk
- 27EG Risk 27/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)Severity59% × 45%Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 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.4%
- EPSS %ILE
- 38th
- 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 (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.9 MEDIUMCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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
November 2, 2026
Advisory Details (10)
Auto-updated Oct 28, 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 ff65e4b0867b (asterisk/asterisk)
Fix landed in asterisk/asterisk commit ff65e4b0867b — awaiting tagged release
https://github.com/asterisk/asterisk/commit/ff65e4b0867bee12cdcb3a6219b976ee7ee08963commit fc3a1cb3c386 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit fc3a1cb3c386 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/fc3a1cb3c386c962bfca8cd9d533d1390d4ad933commit d803b5370b05 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit d803b5370b05 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/d803b5370b05f39a6241b2556eb9894b02148e6acommit ce6e2233599b (asterisk/asterisk)
Fix landed in asterisk/asterisk commit ce6e2233599b — awaiting tagged release
https://github.com/asterisk/asterisk/commit/ce6e2233599b76bc30c33b4816b15609c8ddc8b6commit 6f414ec771ea (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 6f414ec771ea — awaiting tagged release
https://github.com/asterisk/asterisk/commit/6f414ec771eaa3318a4b2d28f70fa387196ae283commit 6da8e10c210d (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 6da8e10c210d — awaiting tagged release
https://github.com/asterisk/asterisk/commit/6da8e10c210d8e014c27c67235252e1dfc794446commit 430f423c84e4 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 430f423c84e4 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/430f423c84e4e32a462d907632b66c9793236e96Weakness 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 20:26 UTCEG score recompute
- 2026-11-02 19:38 UTCEG score recompute
- 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-10-27 18:01 UTCENISA EUVD ID recordedEUVD-2026-111217 · Source: ENISA EUVD
- 2026-10-27 17:26 UTCEG score recompute
- 2026-10-27 16:59 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
- 2026-10-27 16:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-57194?
When was the CVE record for CVE-2026-57194 published?
Is CVE-2026-57194 actively exploited?
What is the CVSS score of CVE-2026-57194?
How do I remediate CVE-2026-57194?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-57194
Is Your Infrastructure Affected by CVE-2026-57194?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.