Quick answers
- Is CVE-2026-57203 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57203 being exploited in the wild.
- How severe is CVE-2026-57203?
- Informational severity, published 27 October 2026.
- Which products and versions are affected?
- Asterisk before 20.20.1, 21.x before 21.12.3, 22.x before 22.10.1, 23.x before 23.4.1; Asterisk Certified Asterisk 20.7 before 20.7-cert11, 22.8 before 22.8-cert3.
- Is there a fix for CVE-2026-57203?
- Yes: fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57203 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-57203?
- Check whether you run Asterisk or Asterisk Certified Asterisk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3
Technical details
The vulnerability is a privilege escalation via insecure temporary file handling (CWE-377). The ast_loggrabber script loads ast_tsconvert.py from /tmp, which is world-writable; an authenticated local attacker can place a malicious Python script there. When an administrator runs ast_loggrabber with elevated privileges, the attacker's code executes with those privileges. The fix moves the script to a secure temporary directory with restrictive permissions.
Affected products
- Asterisk Asterisk before 20.20.1, 21.x before 21.12.3, 22.x before 22.10.1, 23.x before 23.4.1
- Asterisk Certified Asterisk 20.7 before 20.7-cert11, 22.8 before 22.8-cert3
Timeline
- 2026-10-27: disclosed