CVE-2026-57203

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-111402 (ENISA EUVD)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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, ast_loggrabber executes a Python script from the world-writable /tmp directory. An attacker already authorized to open a shell session on the Asterisk server may place a malicious script there and gain elevated privileges or execute code when an administrator runs ast_loggrabber as a user with elevated privileges. 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.

CVSS v3
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
31
EG Risk 31/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)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.1%
EPSS %ILE
3rd
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 (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 29, 2026

Advisory Details (10)

Auto-updated Oct 27, 2026
Patch available. Sources: github_commit, github_release.
GitHub release Patch Available

Asterisk Release 23.4.1

Patch available: asterisk/asterisk 23.4.1

https://github.com/asterisk/asterisk/releases/tag/23.4.1
GitHub release Patch Available

Asterisk Release 22.10.1

Patch available: asterisk/asterisk 22.10.1

https://github.com/asterisk/asterisk/releases/tag/22.10.1
GitHub release Patch Available

Asterisk Release 21.12.3

Patch available: asterisk/asterisk 21.12.3

https://github.com/asterisk/asterisk/releases/tag/21.12.3
GitHub release Patch Available

Asterisk Release 20.20.1

Patch available: asterisk/asterisk 20.20.1

https://github.com/asterisk/asterisk/releases/tag/20.20.1
GitHub commit

commit f18ac4c96478 (asterisk/asterisk)

Fix landed in asterisk/asterisk commit f18ac4c96478 — awaiting tagged release

https://github.com/asterisk/asterisk/commit/f18ac4c964781f671e400342790bf40679698067
GitHub commit

commit c0fc2ae54cb6 (asterisk/asterisk)

Fix landed in asterisk/asterisk commit c0fc2ae54cb6 — awaiting tagged release

https://github.com/asterisk/asterisk/commit/c0fc2ae54cb6289a48a80333432f5fdf5a40c7de
GitHub commit

commit bd63fe121d0e (asterisk/asterisk)

Fix landed in asterisk/asterisk commit bd63fe121d0e — awaiting tagged release

https://github.com/asterisk/asterisk/commit/bd63fe121d0e86867863bd98b5771e592273b035
GitHub commit

commit ba8e5bdecd52 (asterisk/asterisk)

Fix landed in asterisk/asterisk commit ba8e5bdecd52 — awaiting tagged release

https://github.com/asterisk/asterisk/commit/ba8e5bdecd5280fc0ab230df59e41ea21b3a052f
GitHub commit

commit a51c4e3d6bcc (asterisk/asterisk)

Fix landed in asterisk/asterisk commit a51c4e3d6bcc — awaiting tagged release

https://github.com/asterisk/asterisk/commit/a51c4e3d6bccce4bc4226c43e78952573a62f165
GitHub commit

commit 022407ec47ad (asterisk/asterisk)

Fix landed in asterisk/asterisk commit 022407ec47ad — awaiting tagged release

https://github.com/asterisk/asterisk/commit/022407ec47adebe27b7ec8bcf5626e5a02fe1551

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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.

  1. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-29 19:26 UTCEG score recompute
  3. 2026-10-29 18:27 UTCEG score recompute
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-27 22:28 UTCEG score recompute
  7. 2026-10-27 22:01 UTCENISA EUVD ID recordedEUVD-2026-111402 · Source: ENISA EUVD
  8. 2026-10-27 21:54 UTCEG score recomputeFirst assessed: 6.9 MEDIUM
  9. 2026-10-27 21:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57203?
CVE-2026-57203 is a medium-severity vulnerability; its CVE record was published on October 27, 2026. 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, astloggrabber executes a Python script from the world-writable /tmp directory. An attacker already authorized to open a shell…
When was the CVE record for CVE-2026-57203 published?
The CVE record for CVE-2026-57203 was published on October 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 29, 2026; the record at its source may have been updated since.
Is CVE-2026-57203 actively exploited?
CVE-2026-57203 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57203?
CVE-2026-57203 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57203?
A fix for CVE-2026-57203 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57203

Explore →

Is Your Infrastructure Affected by CVE-2026-57203?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.