Cyber Resilience

CVE-2026-23740

Sangoma Certified Asterisk 13.13.0 … 20.7

Published
06 February 2026
Modified
10 February 2026
Patch / advisory
CVSS Score v3.1 0.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:N
EPSS Score 0.0011 2th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-23740 is a uncategorised-severity Uncontrolled Search Path Element (CWE-427) vulnerability in Sangoma Certified Asterisk. Its CVSS base score is 0.0.

Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-23740 is a vulnerability in Asterisk, an open source private branch exchange and telephony toolkit. It affects the ast_coredumper component, which writes gdb init and output files to world-writable directories such as /tmp in versions prior to 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2. The flaw, classified as CWE-427 (Untrusted Search Path), allows manipulation of these file paths when the directory permits writes from unprivileged users.

Any local user on a Linux system with write access to the target directory, such as /tmp, can exploit the vulnerability. By controlling the gdb init file and output paths, the attacker can trick the root-privileged ast_coredumper into executing arbitrary commands or overwriting arbitrary files. The CVSS v3.1 base score is 0.0 (AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:N), indicating a local attack with low complexity, no privileges required, user interaction needed, and changed scope but no direct confidentiality, integrity, or availability impact.

The official Asterisk security advisory at https://github.com/asterisk/asterisk/security/advisories/GHSA-xpc6-x892-v83c confirms the issue has been addressed in versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2. Practitioners should upgrade affected installations to these patched releases to prevent exploitation.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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, when ast_coredumper writes its gdb init and output files to a directory that is world-writable (for example /tmp), an attacker…

more

with write permission(which is all users on a linux system) to that directory can cause root to execute arbitrary commands or overwrite arbitrary files by controlling the gdb init file and output paths. This issue has been patched in versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1034 Path Interception Persistence
**This technique has been deprecated.
T1574.007 Path Interception by PATH Environment Variable Stealth
Adversaries may execute their own malicious payloads by hijacking environment variables used to load libraries.
T1574.008 Path Interception by Search Order Hijacking Stealth
Adversaries may execute their own malicious payloads by hijacking the search order used to load other programs.
T1574 Hijack Execution Flow Stealth
Adversaries may execute their own malicious payloads by hijacking the way operating systems run programs.
T1574.001 DLL Stealth
Adversaries may abuse dynamic-link library files (DLLs) in order to achieve persistence, escalate privileges, and evade defenses.
T1574.004 Dylib Hijacking Stealth
Adversaries may execute their own payloads by placing a malicious dynamic library (dylib) with an expected name in a path a victim application searches at runtime.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-23741Same product: Sangoma Asterisk
CVE-2025-1131Same product: Sangoma Asterisk
CVE-2025-47780Same product: Sangoma Asterisk
CVE-2025-54995Same product: Sangoma Asterisk
CVE-2026-23739Same product: Sangoma Asterisk
CVE-2024-42491Same product: Sangoma Asterisk
CVE-2026-23738Same product: Sangoma Asterisk
CVE-2025-47779Same product: Sangoma Asterisk
CVE-2025-49832Same product: Sangoma Asterisk
CVE-2024-57520Same product: Sangoma Asterisk

Affected Assets

sangoma
certified asterisk
13.13.0, 16.8, 16.8.0, 18.9, 20.7
sangoma
asterisk
≤ 20.18.2 · 21.0.0 — 21.12.1 · 22.0.0 — 22.8.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

Establishes restrictive configuration settings that can define and lock down approved search paths.

Enforces approved authorizations so that only intended actors can place or modify elements in the search path.

Limits privileges so unintended actors cannot write to or control directories in the product's search path.

Restricts logical and physical access to change system configuration, including search-path settings and directories.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices directly address design of search paths and resource loading.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce safe search-path settings and reduce exposure.

PR.PS-05 partial match
prevents

Execution allow-listing can block malicious binaries placed in hijackable search locations.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect uncontrolled search-path issues but does not prevent them by itself.

mitigates

Restricting software installation reduces the chance that an attacker-controlled path element is introduced into the search path.

mitigates

Secure system architecture and engineering principles require explicit control over search paths and resource locations.

prevents

Secure coding practices directly address the use of fixed or controlled search paths that can be influenced by unintended actors.

prevents

Configuration management can enforce approved search-path settings but does not inherently prevent the weakness.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248577 OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. prevents CWE-427

References