CVE-2026-57185

Asterisk: Buffer over-read in Asterisk PJSIP MWI body parser

Published Oct 27, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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 20.7-cert11, 22.8-cert3, an authenticated attacker may crash Asterisk through a buffer over-read in the `PJSIP MWI body parser` by sending a carefully crafted `SIP NOTIFY` request. The attacker must pass SIP authentication using either a username/password or `source IP address matching`. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3.

Analysis

AI-generated

Technical impact

A buffer over-read within the PJSIP MWI body parser of Asterisk allows an authenticated caller to send a specially crafted SIP NOTIFY request that forces the Asterisk process to crash. The defect is a classic buffer under-read (CWE‑125) combined with improper bounds checking (CWE‑126), causing denial of service without providing code execution. The impact is a loss of telephony service for affected hosts, potentially disrupting customer reachability.

Affected Systems

The vulnerability affects the open‑source Asterisk PBX and its certified releases. Versions older than 20.20.1, 21.12.3, 22.10.1, 23.4.1, and the corresponding Certified Asterisk 20.7‑cert11 and 22.8‑cert3 contain the flaw. All later releases include a fix that prevents the over-read and the crash.

Risk and Exploitability

The CVSS score is 6.5, indicating moderate severity, and the EPSS score is under 1 %, signifying a low probability of exploitation in the wild. An attacker must first authenticate with the SIP server, either by supplying valid credentials or by matching the source IP address as configured. Because credentials are required, external opportunistic exploitation is limited, and no ready‑made exploitation tool is publicly available. The vulnerability is not listed in CISA’s KEV catalog, suggesting it has not been broadly exploited.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to any of the patched Asterisk releases (20.20.1, 21.12.3, 22.10.1, 23.4.1, or the corresponding Certified Asterisk 20.7‑cert11, 22.8‑cert3).
  • If an upgrade is not immediately possible, restrict source‑IP based authentication or enforce stricter credential validation to limit the set of users capable of sending SIP NOTIFY messages.
  • Implement firewall or SIP ACL rules to block unsolicited or unauthenticated SIP traffic, ensuring that only known and trusted endpoints can communicate with the Asterisk server.

Generated by OpenCVE AI on November 2, 2026 at 14:31 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Asterisk
Asterisk asterisk
Asterisk certified Asterisk
Vendors & Products Asterisk
Asterisk asterisk
Asterisk certified Asterisk
Type Values Removed Values Added
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 20.7-cert11, 22.8-cert3, an authenticated attacker may crash Asterisk through a buffer over-read in the `PJSIP MWI body parser` by sending a carefully crafted `SIP NOTIFY` request. The attacker must pass SIP authentication using either a username/password or `source IP address matching`. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3.
Title Asterisk: Buffer over-read in Asterisk PJSIP MWI body parser
Weaknesses CWE-126
CWE-170
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 8:21 PM
Reserved
Jun 24, 2026, 1:47 AM
Status
Undergoing Analysis
Published
Oct 27, 2026, 5:17 PM
Modified
Oct 30, 2026, 9:16 PM
Severity
Moderate
Public date
Oct 27, 2026, 4:40 PM