Authorization bypass in Asterisk ARI may allow remote code execution
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-863.
Summary
Asterisk before 20.20.1, from 21.0.0-pre1 before 21.12.3, from 22.0.0-pre1 before 22.10.1, and from 23.0.0-pre1 before 23.4.1, plus Certified Asterisk from 22.8-cert1-pre1 before 22.8-cert3, are affected. An authenticated attacker with read-only ARI permissions can perform write operations through REST-over-WebSocket because of an incorrect authorization check (CWE-863). The bypass lets the attacker load modules from an arbitrary path, which can lead to remote code execution under certain conditions. The HTTP server must be enabled and reachable, and the attacker must already hold valid read-only ARI credentials.
Written with Claude Haiku 5.5 from the sources below · 2026-11-02
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| asterisk | asterisk | before 20.20.1; 21.0.0-pre1 to before 21.12.3; 22.0.0-pre1 to before 22.10.1; 23.0.0-pre1 to before 23.4.1 | 20.20.1, 21.12.3, 22.10.1, 23.4.1 | Patch available | CNA |
| certified-asterisk | certified-asterisk | 22.8-cert1-pre1 to before 22.8-cert3 | 22.8-cert3 | Patch available | CNA |
- asterisk Vendorasterisk Affected before 20.20.1; 21.0.0-pre1 to before 21.12.3; 22.0.0-pre1 to before 22.10.1; 23.0.0-pre1 to before 23.4.1 Fixed in 20.20.1, 21.12.3, 22.10.1, 23.4.1 Patch available CNA
- certified-asterisk Vendorcertified-asterisk Affected 22.8-cert1-pre1 to before 22.8-cert3 Fixed in 22.8-cert3 Patch available CNA
Remediation
Upgrade Asterisk to 20.20.1, 21.12.3, 22.10.1 or 23.4.1, and upgrade Certified Asterisk to 22.8-cert3.
Written with Claude Haiku 5.5 from the sources below · 2026-11-02
- Fix · CNA asterisk (asterisk) Fixed in 20.20.1, 21.12.3, 22.10.1, 23.4.1
- Fix · CNA certified-asterisk (certified-asterisk) Fixed in 22.8-cert3
Vendor assessments
Timeline
- 2026-10-27 Threatist record created from CVE-2026-57200
- 2026-10-28 Priority changed: MEDIUM → LOW
- 2026-10-30 CISA SSVC decision points changed
- 2026-11-02 Affected versions changed · Red Hat
- 2026-11-02 CVSS score added · Red Hat
References
Other 13
- https://github.com/asterisk/asterisk/security/advisories/GHSA-wcvv-g26m-wx5c
- https://github.com/asterisk/asterisk/commit/051d29a0d35559e9165bab346de9422e25415533
- https://github.com/asterisk/asterisk/commit/205c301a0a0b0d013d4ebdf12856ebbc30405350
- https://github.com/asterisk/asterisk/commit/762b4c9c39b28fa5564112b0f484012298469a6c
- https://github.com/asterisk/asterisk/commit/87641e9b2cd62c998c5283400ba77b61b5b07dd4
- https://github.com/asterisk/asterisk/commit/9d198a7d16ccba51507dfea6c1ecc511e89d698a
- https://github.com/asterisk/asterisk/commit/c10cdbce072a708060cd38a89d6850808fe6bf46
- https://github.com/asterisk/asterisk/releases/tag/20.20.1
- https://github.com/asterisk/asterisk/releases/tag/21.12.3
- https://github.com/asterisk/asterisk/releases/tag/22.10.1
- https://github.com/asterisk/asterisk/releases/tag/23.4.1
- https://github.com/asterisk/asterisk/releases/tag/certified-22.8-cert3
- https://github.com/asterisk/asterisk/tree/24.0.0-pre1
More asterisk vulnerabilities
- TI-2025-30244 Using malformed From header can forge identity with ";" or NULL in name portion CVSS 3.1HIGH 7.7
- TI-2023-27195 Asterisk susceptible to Denial of Service via DTLS Hello packets during call initiation CVSS 3.1HIGH 7.5
- TI-2024-28351 Asterisk allows `Write=originate` as sufficient permissions for code execution / `System()` dialplan CVSS 3.1HIGH 8.8
- TI-2025-00959 Asterisk Unsafe Shell Sourcing in safe_asterisk Leads to Local Privilege Escalation CVSS 4.0HIGH 7.0
- TI-2025-34699 Asterisk remotely exploitable leak of RTP UDP ports and internal resources CVSS 3.1MEDIUM 6.5
- TI-2025-31747 Asterisk is Vulnerable to Remote DoS and possible RCE Attacks During Memory Allocation CVSS 3.1MEDIUM 6.5
Sources
- CVE-2026-57200 · CVE Program
- CVE-2026-57200 · NVD
- FIRST EPSS
- CVE-2026-57200 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences