CVE-2026-57186 — Asterisk: CVE-2022-37325 fix is absent from current chan_ooh323 Q.931 party-number parser
Asterisk is an open source private branch exchange and telephony toolkit. From 21.0.0-pre1 until Asterisk 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 22.8-cert3, the `chan_ooh323` `Q.931 party-number parser` lacks the `CVE-2022-37325` fix because that fix was never forward-ported from Asterisk 20 to later versions. Malformed Q.931 elements in an `OOH323 request` can therefore crash Asterisk. This issue affects Asterisk versions greater than 20. 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 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 22.8-cert3.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Asterisk Asterisk, Asterisk Certified-asterisk).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Asterisk | Asterisk | version >= 21.0.0-pre1, < 21.12.3version >= 22.0.0-pre1, < 22.10.1version >= 23.0.0-pre1, < 23.4.1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Asterisk | Certified-asterisk | version >= 22.8-cert1-pre1, < 22.8-cert3 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | security-advisories@github.com via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · asterisk/asterisk, asterisk/certified-asterisk
- Record published
- CVSS changed · 7.5
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 27, 2026 – Oct 27, 2026
- 1× Official description updated · Oct 27, 2026 – Oct 27, 2026
References
11 on the record
- github.com/asterisk/asterisk/commit/0e776a837106d5d0d14503a53388337931045164
- github.com/asterisk/asterisk/releases/tag/23.4.1
- github.com/asterisk/asterisk/security/advisories/GHSA-h5hv-jmgj-92q2
- github.com/asterisk/asterisk/commit/07b9740cbc371ffa7936cf368089fd073250ea7c
- github.com/asterisk/asterisk/commit/46c6c652d1de9bfbb061fab0b1f681cf60660998
- github.com/asterisk/asterisk/commit/42d3552d2ac0efbb68c9ec7ade898b6de0bfa033
- github.com/asterisk/asterisk/releases/tag/certified-22.8-cert3
- github.com/asterisk/asterisk/commit/62a7a7037b1a145cabf95895b119cbae4d3c5a4f
- github.com/asterisk/asterisk/releases/tag/21.12.3
- github.com/asterisk/asterisk/tree/24.0.0-pre1
- github.com/asterisk/asterisk/releases/tag/22.10.1
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-57192 Asterisk: Out-of-Bounds Write in Codec2 Decoder Due to Floor/Ceil Sample Count Mismatch 4h
- High CVE-2026-57190 Asterisk: SQL Injection in cel_pgsql and cel_tds via CELGenUserEvent eventtype Field 4h
- High CVE-2026-57191 Asterisk: Stack buffer overflow in MWI NOTIFY Message-Account parsing 4h
- Medium CVE-2026-57203 Asterisk: Local privilege escalation through ast_loggrabber's world-writable helper location 4h
- Low CVE-2026-57199 Asterisk: Asterisk app_sms.c copies externally controlled SMS lengths into fixed in-struct buffers 4h
- High CVE-2026-57195 Asterisk: NULL Pointer Dereference in HTTP AMI Digest Authentication 4h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-57186 is "Asterisk: CVE-2022-37325 fix is absent from current chan_ooh323 Q.931 party-number parser", rated High. It affects Asterisk (Asterisk); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.