Asterisk: ARI REST-over-WebSocket read-only bypass allows arbitrary module path load and conditional RCE
Summary
| CVE | CVE-2026-57200 |
|---|---|
| State | PUBLISHED |
| Assigner | GitHub_M |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-27 21:18:06 UTC |
| Updated | 2026-10-30 21:17:12 UTC |
| Description | 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 22.8-cert3, an authenticated attacker with read-only permissions for the `Asterisk REST Interface (ARI)` may, under certain conditions, execute write operations through `REST-over-WebSocket`. The authorization bypass permits `arbitrary module path` loading and conditional remote code execution. The Asterisk HTTP web server must be enabled and reachable, and the attacker must already have valid `read-only ARI credentials`. HTTP is disabled by default and binds only to 127.0.0.1 by default even when enabled. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 22.8-cert3. |
Risk And Classification
Primary CVSS: v3.1 7.5 HIGH from [email protected]
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.008790000 probability, percentile 0.590920000 (date 2026-11-02)
Problem Types: CWE-22 | CWE-863 | CWE-22 CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | CWE-863 CWE-863: Incorrect Authorization
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 7.5 | HIGH | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 7.5 | HIGH | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
HighPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Asterisk | Asterisk | affected < 20.20.1 | Not specified |
| CNA | Asterisk | Asterisk | affected >= 21.0.0-pre1, < 21.12.3 | Not specified |
| CNA | Asterisk | Asterisk | affected >= 22.0.0-pre1, < 22.10.1 | Not specified |
| CNA | Asterisk | Asterisk | affected >= 23.0.0-pre1, < 23.4.1 | Not specified |
| CNA | Certified-asterisk | Certified-asterisk | affected >= 22.8-cert1-pre1, < 22.8-cert3 | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/asterisk/asterisk/security/advisories/GHSA-wcvv-g26m-wx5c | [email protected] | github.com | |
| github.com/asterisk/asterisk/commit/c10cdbce072a708060cd38a89d6850808fe6... | [email protected] | github.com | |
| github.com/asterisk/asterisk/releases/tag/22.10.1 | [email protected] | github.com | |
| github.com/asterisk/asterisk/commit/051d29a0d35559e9165bab346de9422e2541... | [email protected] | github.com | |
| github.com/asterisk/asterisk/releases/tag/20.20.1 | [email protected] | github.com | |
| github.com/asterisk/asterisk/commit/9d198a7d16ccba51507dfea6c1ecc511e89d... | [email protected] | github.com | |
| github.com/asterisk/asterisk/commit/762b4c9c39b28fa5564112b0f48401229846... | [email protected] | github.com | |
| github.com/asterisk/asterisk/releases/tag/certified-22.8-cert3 | [email protected] | github.com | |
| github.com/asterisk/asterisk/commit/205c301a0a0b0d013d4ebdf12856ebbc3040... | [email protected] | github.com | |
| github.com/asterisk/asterisk/releases/tag/23.4.1 | [email protected] | github.com | |
| github.com/asterisk/asterisk/releases/tag/21.12.3 | [email protected] | github.com | |
| github.com/asterisk/asterisk/commit/87641e9b2cd62c998c5283400ba77b61b5b0... | [email protected] | github.com | |
| github.com/asterisk/asterisk/tree/24.0.0-pre1 | [email protected] | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.