Asterisk: Out-of-Bounds Read in Q.931 Information Element Parser (H.323 Addon) (CVE-2026-57184)
Published Last modified Sources: BSI, CVE.org
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 20.7-cert11, 22.8-cert3, insufficient bounds checking in the `chan_ooh323` `Q.931` `information-element parser` permits an `out-of-bounds read` that may allow an unauthenticated attacker to crash Asterisk using carefully crafted `setup packets`.
Update Asterisk to version 20.20.1, Asterisk Certified-asterisk to version 20.7-cert11.
- Affected
- Asterisk
gte 21.0.0-pre1, < 21.12.3..* - Asterisk
lt *..20.20.1 - Asterisk Certified-asterisk
gte 22.8-cert1-pre1, < 22.8-cert3..* - Asterisk Certified-asterisk
lt *..20.7-cert11
- Asterisk
- Fixed in
- Asterisk
20.20.1 - Asterisk Certified-asterisk
20.7-cert11
- Asterisk
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
6.3
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v4
6.3
CVSS v4
Severity Medium on the scale from 0 to 10.
Source: BSI, CVE.org
0.6 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 46.5
Show all metrics
- Severity
- Medium
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- 78.79 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- 6.3 Methodology
CVSS v4
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- 6.3
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.6 %
- 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- 46.5
- 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
- CISA assessment (SSVC)
- Exploitation: none known · automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 26 October 2026
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-125
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- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
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 20.7-cert11, 22.8-cert3, insufficient bounds checking in the `chan_ooh323` `Q.931` `information-element parser` permits an `out-of-bounds read` that may allow an unauthenticated attacker to crash Asterisk using carefully crafted `setup packets`. The `chan_ooh323` addon channel driver must be explicitly compiled and installed, which is not the default, and its port must be publicly reachable. 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.
Source: BSI WID Portal, BSI CSAF, cvelistv5, NVD (NIST), CVE.org (MITRE)
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 |
|
|
| asterisk | certified-asterisk |
|
|
Vendors and products
Weakness classes (CWE)
CWE-125Out-of-bounds Read
Base
The product reads data past the end, or before the beginning, of the intended buffer.
Entry at MITRE CWE-125
References & sources
- github.comasterisk/asterisk/security/advisories/GHSA-746q-794h-cc7fx_refsource_CONFIRM
- github.comasterisk/asterisk/commit/00ebdfbc89ed160ae45a2fc0f67f36e36dae48…x_refsource_MISC
- github.comasterisk/asterisk/commit/437d17fb13503fe9b4e72c35396f0c250d30b0…x_refsource_MISC
- github.comasterisk/asterisk/commit/6dba027f8aea35bf3bbd89371a0cf516b13f85…x_refsource_MISC
- github.comasterisk/asterisk/commit/9c776e348374a72589cf27f635cddef45a2a2b…x_refsource_MISC
- github.comasterisk/asterisk/commit/ad4a2b3e944afd5a8e9a550bd5f62aeac86807…x_refsource_MISC
- github.comasterisk/asterisk/commit/b1284510421a29c72fc4e9a31e4b1e0666a014…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-20.7-cert11x_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).
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: yes
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-57184","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-26T20:22:44.213207Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedGitHub
CVSS V4.0: AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Weakness type: CWE-125
Description added or changed
New references:- https://github.com/asterisk/asterisk/commit/00ebdfbc89ed160ae45a2fc0f67f36e36dae48ee
- https://github.com/asterisk/asterisk/commit/437d17fb13503fe9b4e72c35396f0c250d30b0f0
- https://github.com/asterisk/asterisk/commit/6dba027f8aea35bf3bbd89371a0cf516b13f8588
- https://github.com/asterisk/asterisk/commit/9c776e348374a72589cf27f635cddef45a2a2b90
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 20.7-cert11, 22.8-cert3, insufficient bounds checking in the `chan_ooh323` `Q.931` `information-element parser` permits an `out-of-bounds read` that may allow an unauthenticated attacker to crash Asterisk using carefully crafted `setup packets`. The `chan_ooh323` addon channel driver must be explicitly compiled and installed, which is not the default, and its port must be publicly reachable. 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.CVSS added —AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XWeakness type (CWE) added —CWE-125Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/57xxx/CVE-2026-57184.json">CVE-2026-57184</a>Reference added —https://github.com/asterisk/asterisk/commit/00ebdfbc89ed160ae45a2fc0f67f36e36dae48eeReference added —https://github.com/asterisk/asterisk/commit/437d17fb13503fe9b4e72c35396f0c250d30b0f0Reference added —https://github.com/asterisk/asterisk/commit/6dba027f8aea35bf3bbd89371a0cf516b13f8588Reference added —https://github.com/asterisk/asterisk/commit/9c776e348374a72589cf27f635cddef45a2a2b90Reference added —https://github.com/asterisk/asterisk/commit/ad4a2b3e944afd5a8e9a550bd5f62aeac8680711Reference added —https://github.com/asterisk/asterisk/commit/b1284510421a29c72fc4e9a31e4b1e0666a0144fReference 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-20.7-cert11Reference added —https://github.com/asterisk/asterisk/releases/tag/certified-22.8-cert3Reference added —https://github.com/asterisk/asterisk/security/advisories/GHSA-746q-794h-cc7fReference 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-57184"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-57184.svg?lang=en" alt="CVE-2026-57184 – NEOSEC Intel" height="20"></a>