# CVE-2026-57186: Asterisk: CVE-2022-37325 fix is absent from current chan_ooh323 Q.931 party-number parser


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 27 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-57186, GHSA-h5hv-jmgj-92q2, UBUNTU-CVE-2026-57186

## What is CVE-2026-57186?

CVE-2026-57186 is a high-severity vulnerability in asterisk, published on 27 Oct 2026. 

### Official description

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.

Weakness: CWE-839 (Numeric Range Comparison Without Minimum Check)

## Which versions are affected by CVE-2026-57186?


## How do I fix CVE-2026-57186?

Upgrade to a fixed version.

## Is CVE-2026-57186 being exploited?

There is no known exploitation of CVE-2026-57186 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57186 and fix it if it is affected.

What it is: CVE-2026-57186 is a high-severity vulnerability in asterisk, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-57186 in the wild and no public exploit code.

Affected product: asterisk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57186/ (Markdown: https://insights.sbomify.com/CVE-2026-57186/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57186
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57186
- OSV: https://osv.dev/vulnerability/CVE-2026-57186

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57186/
Summaries are generated and may contain mistakes; the official description above is the record.