Skip to content
Fencer Intel
high 8.1

CVE-2026-57202 json

Asterisk: ARI setChannelVar bypasses live_dangerously and permits FILE() writes

published 4mo ago modified 14d ago also EUVD-2026-111345 , GHSA-vrfp-mg3q-3959

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository asterisk/asterisk. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

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, an authenticated Asterisk REST Interface (ARI) attacker with read-only privileges may use `setChannelVar` to execute write dialplan functions, including `FILE()` writes, even when `live_dangerously` in `asterisk.conf` is set to no. 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 20.7-cert11, 22.8-cert3.

Patch / fix

  • digium certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
  • sangoma certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
  • digium asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1
  • asterisk open_source 20.20.1, 21.12.3, 22.10.1, 23.4.1
  • asterisk certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
  • asterisk Debian 14 1:22.10.1+dfsg+~cs6.17.60671434-1

debian advisories DEBIAN-CVE-2026-57202

Is CVE-2026-57202 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-57202 updated cvss 8.1

asterisk: Asterisk: Privilege escalation via setChannelVar in Asterisk REST Interface

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
14d ago

Exploit prediction

0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

  • asterisk asterisk
  • asterisk certified-asterisk

Classification

Weakness
  • CWE-267 Privilege Defined With Unsafe Actions
  • CWE-1220 Insufficient Granularity of Access Control

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of asterisk/asterisk published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.