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, a stack buffer overflow in the H.323 ooTrace() trace-logging function can occur when unbounded vsprintf writes into a fixed 2048-byte buffer. A remote attacker may send a carefully crafted packet that causes the Asterisk process to crash. The chan_ooh323 addon channel driver must be explicitly compiled and installed, which is not the default, and its port must be publicly reachable. 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-57201
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-111220 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 49EG Risk 49/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)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 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.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.7%
- EPSS %ILE
- 53rd
- 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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 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-30). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 30, 2026
Advisory Details (10)
Auto-updated Oct 27, 2026Asterisk 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 fff256d0539e (asterisk/asterisk)
Fix landed in asterisk/asterisk commit fff256d0539e — awaiting tagged release
https://github.com/asterisk/asterisk/commit/fff256d0539e96f70ac315844d72e9d540f03a4ccommit c4d9b4defe83 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit c4d9b4defe83 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/c4d9b4defe83f74523880fd630c02c49683786a3commit bf0c9a906892 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit bf0c9a906892 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/bf0c9a906892bc0f91fa753476e326919e4e30e5commit ac0a64dec6d4 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit ac0a64dec6d4 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/ac0a64dec6d4231bf005a68da6af3e02bb311634commit 875ac7413de0 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 875ac7413de0 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/875ac7413de0b7068cd12d0da2f140cd06ba9357commit 33f62e351642 (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 33f62e351642 — awaiting tagged release
https://github.com/asterisk/asterisk/commit/33f62e351642edd9c58ef97b0002132722546af9commit 2d7b8c8dc13d (asterisk/asterisk)
Fix landed in asterisk/asterisk commit 2d7b8c8dc13d — awaiting tagged release
https://github.com/asterisk/asterisk/commit/2d7b8c8dc13d9ead8b6f36cc38b6dd91cd4abd3aStack Buffer Overflow in H.323 ooTrace() via Unbounded vsprintf into Fixed 2048-byte Buffer · Advisory · asterisk/asterisk · GitHub
https://github.com/asterisk/asterisk/security/advisories/GHSA-x348-j6c9-77f3Weakness 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% · 53rd percentile
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-30 21:26 UTCEG score recompute
- 2026-10-30 20:29 UTCEG score recompute
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-27 18:01 UTCENISA EUVD ID recordedEUVD-2026-111220 · Source: ENISA EUVD
- 2026-10-27 17:26 UTCEG score recompute
- 2026-10-27 16:59 UTCEG score recomputeFirst assessed: 7.5 HIGH
- 2026-10-27 16:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-57201?
When was the CVE record for CVE-2026-57201 published?
Is CVE-2026-57201 actively exploited?
What is the CVSS score of CVE-2026-57201?
How do I remediate CVE-2026-57201?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-57201
Is Your Infrastructure Affected by CVE-2026-57201?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.