CVE-2026-57200: Asterisk: ARI REST-over-WebSocket read-only bypass allows arbitrary module path load and conditional RCE

Published Oct 27, 2026
·
Updated

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.

Affected Software

2 affected components
Asterisk Asterisk<20.20.1, <21.12.3, <22.10.1, <23.4.1
Asterisk Certified Asterisk<22.8-cert3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Asterisk to a version that resolves this vulnerability.

    Fixed in 20.20.1
  2. Upgrade

    Upgrade Asterisk to a version that resolves this vulnerability.

    Fixed in 21.12.3
  3. Upgrade

    Upgrade Asterisk to a version that resolves this vulnerability.

    Fixed in 22.10.1
  4. Upgrade

    Upgrade Asterisk to a version that resolves this vulnerability.

    Fixed in 23.4.1
  5. Upgrade

    Upgrade Certified Asterisk to a version that resolves this vulnerability.

    Fixed in 22.8-cert3

Event History

Oct 27, 2026
CVE Published
via MITRE·09:13 PM
Data Sourced
via MITRE·09:13 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are realistically exposed?

Exposure requires the Asterisk HTTP web server to be enabled and reachable, plus valid read-only ARI credentials. HTTP is disabled by default and, when enabled, binds to 127.0.0.1 by default, so instances retaining those defaults are not remotely reachable through the HTTP service.

2

What does an attacker need to exploit this issue?

An attacker needs valid credentials that have read-only permissions for the Asterisk REST Interface (ARI). Exploitation also depends on the HTTP web server being enabled and reachable, and succeeds only under certain conditions.

3

Can read-only ARI access lead to code execution?

Yes. The REST-over-WebSocket authorization bypass can allow write operations despite read-only ARI permissions, including loading an arbitrary module path; this can conditionally result in remote code execution.

4

What versions contain the fix?

The issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, and 23.4.1, as well as Certified Asterisk 22.8-cert3.

5

What can be done if updating immediately is not possible?

Disable the Asterisk HTTP web server if it is not required. If it must remain enabled, ensure it is not reachable by untrusted parties and restrict access to valid ARI credentials, particularly accounts granted read-only ARI permissions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203