Asterisk: Path Traversal (CVE-2026-57200)
Published Last modified Sources: CVE.org, BSI
What is affected, what to do
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 22.8-cert3, an authenticated attacker with read-only permissions for the `Asterisk REST Interface (ARI)` may, under certain conditions, execute write operations through `REST-over-WebSocket`.
Update Asterisk to version 20.20.1.
- Affected
- Asterisk
gte 21.0.0-pre1, < 21.12.3..* - Asterisk
lt *..20.20.1 - Certified-asterisk
gte 22.8-cert1-pre1, < 22.8-cert3..*
- Asterisk
- Fixed in
- Asterisk
20.20.1
- Asterisk
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.5
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
7.5
CVSS v3
Severity High on the scale from 0 to 10.
Source: CVE.org, BSI
0.9 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 59.0
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 95.35 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.5
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.9 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 59.0
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-22, CWE-863
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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 22.8-cert3, an authenticated attacker with read-only permissions for the `Asterisk REST Interface (ARI)` may, under certain conditions, execute write operations through `REST-over-WebSocket`. The authorization bypass permits `arbitrary module path` loading and conditional remote code execution. The Asterisk HTTP web server must be enabled and reachable, and the attacker must already have valid `read-only ARI credentials`. HTTP is disabled by default and binds only to 127.0.0.1 by default even when enabled. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 22.8-cert3.
Source: NVD (NIST), cvelistv5, CVE.org (MITRE), BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| asterisk | asterisk |
|
|
| certified-asterisk | certified-asterisk |
|
|
Vendors and products
Weakness classes (CWE)
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Base
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Entry at MITRE CWE-22CWE-863Incorrect Authorization
Class
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Entry at MITRE CWE-863
References & sources
- github.comasterisk/asterisk/security/advisories/GHSA-wcvv-g26m-wx5cx_refsource_CONFIRM
- github.comasterisk/asterisk/commit/051d29a0d35559e9165bab346de9422e254155…x_refsource_MISC
- github.comasterisk/asterisk/commit/205c301a0a0b0d013d4ebdf12856ebbc304053…x_refsource_MISC
- github.comasterisk/asterisk/commit/762b4c9c39b28fa5564112b0f484012298469a…x_refsource_MISC
- github.comasterisk/asterisk/commit/87641e9b2cd62c998c5283400ba77b61b5b07d…x_refsource_MISC
- github.comasterisk/asterisk/commit/9d198a7d16ccba51507dfea6c1ecc511e89d69…x_refsource_MISC
- github.comasterisk/asterisk/commit/c10cdbce072a708060cd38a89d6850808fe6bf…x_refsource_MISC
- github.comasterisk/asterisk/releases/tag/20.20.1x_refsource_MISC
- github.comasterisk/asterisk/releases/tag/21.12.3x_refsource_MISC
- github.comasterisk/asterisk/releases/tag/22.10.1x_refsource_MISC
- github.comasterisk/asterisk/releases/tag/23.4.1x_refsource_MISC
- github.comasterisk/asterisk/releases/tag/certified-22.8-cert3x_refsource_MISC
- github.comasterisk/asterisk/tree/24.0.0-pre1x_refsource_MISC
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
ReceivedGitHub
CVSS V3.1: AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness type: CWE-22, CWE-863
Description added or changed
New references:- https://github.com/asterisk/asterisk/commit/051d29a0d35559e9165bab346de9422e25415533
- https://github.com/asterisk/asterisk/commit/205c301a0a0b0d013d4ebdf12856ebbc30405350
- https://github.com/asterisk/asterisk/commit/762b4c9c39b28fa5564112b0f484012298469a6c
- https://github.com/asterisk/asterisk/commit/87641e9b2cd62c998c5283400ba77b61b5b07dd4
and 8 more references
Show 18 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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 22.8-cert3, an authenticated attacker with read-only permissions for the `Asterisk REST Interface (ARI)` may, under certain conditions, execute write operations through `REST-over-WebSocket`. The authorization bypass permits `arbitrary module path` loading and conditional remote code execution. The Asterisk HTTP web server must be enabled and reachable, and the attacker must already have valid `read-only ARI credentials`. HTTP is disabled by default and binds only to 127.0.0.1 by default even when enabled. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 22.8-cert3.CVSS added —AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HWeakness type (CWE) added —CWE-22Weakness type (CWE) added —CWE-863Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/57xxx/CVE-2026-57200.json">CVE-2026-57200</a>Reference added —https://github.com/asterisk/asterisk/commit/051d29a0d35559e9165bab346de9422e25415533Reference added —https://github.com/asterisk/asterisk/commit/205c301a0a0b0d013d4ebdf12856ebbc30405350Reference added —https://github.com/asterisk/asterisk/commit/762b4c9c39b28fa5564112b0f484012298469a6cReference added —https://github.com/asterisk/asterisk/commit/87641e9b2cd62c998c5283400ba77b61b5b07dd4Reference added —https://github.com/asterisk/asterisk/commit/9d198a7d16ccba51507dfea6c1ecc511e89d698aReference added —https://github.com/asterisk/asterisk/commit/c10cdbce072a708060cd38a89d6850808fe6bf46Reference added —https://github.com/asterisk/asterisk/releases/tag/20.20.1Reference added —https://github.com/asterisk/asterisk/releases/tag/21.12.3Reference added —https://github.com/asterisk/asterisk/releases/tag/22.10.1Reference added —https://github.com/asterisk/asterisk/releases/tag/23.4.1Reference added —https://github.com/asterisk/asterisk/releases/tag/certified-22.8-cert3Reference added —https://github.com/asterisk/asterisk/security/advisories/GHSA-wcvv-g26m-wx5cReference added —https://github.com/asterisk/asterisk/tree/24.0.0-pre1Source identifier: security-advisories@github.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-57200"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-57200.svg?lang=en" alt="CVE-2026-57200 – NEOSEC Intel" height="20"></a>