CVE-2026-23741

ast_coredumper running as root sources ast_debug_tools.conf from /etc/asterisk; potentially leading to privilege escalation

HIGH
8.8
CVSS Score
Published: February 6, 2026 at 04:47 PM UTC
Updated: June 17, 2026 at 10:22 AM UTC
3 products affected across 2 vendorsAsteriskCertified AsteriskAsterisk

Using asterisk by asterisk?

Get instant alerts when new vulnerabilities affect asterisk - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Asterisk is an open source private branch exchange and telephony toolkit. Prior to versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2, the asterisk/contrib/scripts/ast_coredumper runs as root, as noted by the NOTES tag on line 689 of the ast_coredumper file. The script will source the contents of /etc/asterisk/ast_debug_tools.conf, which resides in a folder that is writeable by the asterisk user:group. Due to the /etc/asterisk/ast_debug_tools.conf file following bash semantics and it being loaded; an attacker with write permissions may add or modify the file such that when the root ast_coredumper is run; it would source and thereby execute arbitrary bash code found in the /etc/asterisk/ast_debug_tools.conf. This issue has been patched in versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 20.18.221.0.0 ≤ v < 21.12.122.0.0 ≤ v < 22.8.223.0.0 ≤ v < 23.2.2
v < 20.18.2v < 20.7-cert9v < 21.12.1v < 22.8.2v < 23.2.2
Affected range stops below 20.18.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.7-cert9, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.12.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.8.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

x_refsource_CONFIRMVendor Advisory
Source: cverecord
https://github.com/asterisk/asterisk/security/advisories/GHSA-rvch-3jmx-3jf3

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-427

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card