Quick answers
- Is CVE-2026-57184 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57184 being exploited in the wild.
- How severe is CVE-2026-57184?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Asterisk Prior to 20.20.1, 21.12.3, 22.10.1, 23.4.1; Asterisk Certified Asterisk Prior to 20.7-cert11, 22.8-cert3.
- Is there a fix for CVE-2026-57184?
- Yes: fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1; Certified Asterisk 20.7-cert11, 22.8-cert3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57184 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-57184?
- 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 20.20.1, 21.12.3, 22.10.1, 23.4.1; Certified Asterisk 20.7-cert11, 22.8-cert3
Technical details
An out-of-bounds read vulnerability exists in the Q.931 information-element parser within the chan_ooh323 channel driver (ooq931.c). The vulnerability stems from insufficient bounds checking in the ooQ931Decode function when parsing incoming setup packets. An unauthenticated attacker on the network can trigger the out-of-bounds read by sending crafted packets, causing a crash; no authentication or user interaction is required.
Affected products
- Asterisk Asterisk Prior to 20.20.1, 21.12.3, 22.10.1, 23.4.1
- Asterisk Certified Asterisk Prior to 20.7-cert11, 22.8-cert3
Timeline
- 2026-10-26: disclosed