Skip to main content
VulnerabilityPublished

CVE-2026-57196: asterisk · Cross-site Scripting

Affects asteriskSource CVE Database V5

0

Not known to be exploited · CVSS 2.3 Low · fixed in 23.4.1 : update asterisk when convenient.

Data as of 26 Oct 2026, 20:42 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 23.4.1, 22.10.1, 21.12.3 +3
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade asterisk to 23.4.1, 22.10.1, 21.12.3 or 20.20.1; certified-asterisk to 22.8-cert3 or 20.7-cert11.

Affected software

ProductAffectedFixed in
asteriskasteriskAffected
  • >=23.0.0-pre1 <23.4.1
Fixed in
  • 23.4.1
asteriskasteriskAffected
  • >=22.0.0-pre1 <22.10.1
Fixed in
  • 22.10.1
asteriskasteriskAffected
  • >=21.0.0-pre1 <21.12.3
Fixed in
  • 21.12.3
asteriskasteriskAffected
  • <20.20.1
Fixed in
  • 20.20.1
asteriskcertified-asteriskAffected
  • >=22.8-cert1-pre1 <22.8-cert3
Fixed in
  • 22.8-cert3
asteriskcertified-asteriskAffected
  • <20.7-cert11
Fixed in
  • 20.7-cert11

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 20.7-cert11, 22.8-cert3, an unauthenticated attacker may use reflected cross-site scripting in `phone provisioning HTTP error pages` to retrieve an authorized user's `AMI session cookie` and impersonate that user when `res_phoneprov` is enabled. The Asterisk HTTP web server, Asterisk Manager Interface (AMI), and AMI access via HTTP must all be enabled; each is disabled by default. The attacker must be able to connect to the HTTP server, which binds only to `127.0.0.1` by default even when enabled, and must convince the authorized user to click a malicious link. 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.

References

Community reviews

Loading reviews…