dbcve.org
AsteriskApplication · Sangoma

CVE-2025-1131

HIGH · 7.8 CVSS v3.1 Published 2025-09-23
Fix available
A fix is available. Upgrade to 18.26.3 / 20.15.1 or later.
See remediation →
80/100
Remediation priority · High
Public exploit Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A local privilege escalation vulnerability exists in the safe_asterisk script included with the Asterisk toolkit package. When Asterisk is started via this script (common in SysV init or FreePBX environments), it sources all .sh files located in /etc/asterisk/startup.d/ as root, without validating ownership or permissions. Non-root users with legitimate write access to /etc/asterisk can exploit this behaviour by placing malicious scripts in the startup.d directory, which will then execute with root privileges upon service restart.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-427

The program loads a library or executable from a location an attacker can influence — a writable directory early in the search order — so a malicious file is loaded with the application's privileges. On Windows this is the classic DLL-hijack. Remediation is loading only from fully-qualified trusted paths and controlling the search order explicitly.

General guidance for the uncontrolled search path (dll hijack) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AsteriskApplication
Affected:< 18.26.3>= 20.0.0, < 20.15.1>= 21.0.0, < 21.10.1>= 22.0.0, < 22.5.1
Certified AsteriskApplication
Affected:= 18.9= 20.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 18.26.3 / 20.15.1 / 21.10.1 or later
Fixed in 18.26.320.15.121.10.1
Recommended fix High confidence

Upgrade to Asterisk 18.26.3, 20.15.1, 21.10.1, or 22.5.1 (or latest certified release for Certified Asterisk 18.9/20.7)

  1. Identify current Asterisk version using 'asterisk -V' or 'asterisk -r -x "core show version"'
  2. Determine which branch you are running (18.x, 20.x, 21.x, or 22.x) to select the appropriate fixed version
  3. Back up all Asterisk configuration files in /etc/asterisk/ and any custom scripts in /etc/asterisk/startup.d/
  4. Upgrade Asterisk to the fixed version: 18.26.3 for 18.x branch, 20.15.1 for 20.x branch, 21.10.1 for 21.x branch, or 22.5.1 for 22.x branch
  5. For Certified Asterisk users: upgrade to the latest available certified version for your branch
  6. After upgrade, verify the fixed version is running with 'asterisk -V'
  7. Audit /etc/asterisk/startup.d/ directory to ensure only trusted, root-owned scripts are present
  8. Restart Asterisk service to confirm normal operation
Caveat Minor version upgrades within the same major branch are typically backward compatible; however, review Asterisk release notes for any module or configuration changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1131 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data