Is CVE-2026-57186 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-57186 being exploited in the wild.

How severe is CVE-2026-57186?

High severity, with a CVSS score of 7.5, published 27 October 2026.

Which products and versions are affected?

Asterisk 21.0.0-pre1 to 21.12.2, 22.0.0 to 22.10.0, 23.0.0 to 23.4.0; Asterisk Certified Asterisk 22.0-cert to 22.8-cert2.

How is CVE-2026-57186 attacked?

It is attacked over the network.

Am I affected by CVE-2026-57186?

Check whether you run Asterisk or Asterisk Certified Asterisk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-57186: Asterisk OOH323 Q.931 parser denial of service

CVE-2026-57186 · Severity: high · CVSS 7.5 · Published 2026-10-27

Asterisk is an open-source PBX and VoIP telephony platform used to route voice calls and messages. The optional OOH323 channel driver fails to validate the length of Q.931 protocol elements, allowing a remote attacker to crash the Asterisk service by sending a specially crafted call request. This affects only installations that have explicitly compiled and enabled the OOH323 addon with a publicly reachable port.

Technologies: Asterisk, Asterisk Certified Asterisk. Vendors: Asterisk.

Quick answers

Is CVE-2026-57186 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57186 being exploited in the wild.
How severe is CVE-2026-57186?: High severity, with a CVSS score of 7.5, published 27 October 2026.
Which products and versions are affected?: Asterisk 21.0.0-pre1 to 21.12.2, 22.0.0 to 22.10.0, 23.0.0 to 23.4.0; Asterisk Certified Asterisk 22.0-cert to 22.8-cert2.
Is there a fix for CVE-2026-57186?: Yes: fixed in Asterisk 21.12.3, 22.10.1, 23.4.1; Certified Asterisk 22.8-cert3. Until then: The chan_ooh323 addon must be explicitly compiled and is not enabled by default; deployments not using OOH323 are unaffected. For affected deployments, restrict network access to the OOH323 port or disable the chan_ooh323 module until patching is possible. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57186 attacked?: It is attacked over the network.
Am I affected by CVE-2026-57186?: Check whether you run Asterisk or Asterisk Certified Asterisk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Asterisk 21.12.3, 22.10.1, 23.4.1; Certified Asterisk 22.8-cert3

The chan_ooh323 addon must be explicitly compiled and is not enabled by default; deployments not using OOH323 are unaffected. For affected deployments, restrict network access to the OOH323 port or disable the chan_ooh323 module until patching is possible.

Technical details

The chan_ooh323 Q.931 party-number parser lacks minimum length validation for calling/called number information elements (IE), allowing malformed Q.931 elements in OOH323 requests to trigger a buffer overflow or out-of-bounds access and crash Asterisk. The vulnerability exists because a prior CVE-2022-37325 fix was never forward-ported from Asterisk 20 to later versions. The attack requires network access to the OOH323 port and does not require authentication.

Affected products

Asterisk Asterisk 21.0.0-pre1 to 21.12.2, 22.0.0 to 22.10.0, 23.0.0 to 23.4.0
Asterisk Certified Asterisk 22.0-cert to 22.8-cert2

Timeline

2026-10-27: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.