CVE-2026-57187 json
Asterisk: Heap-use-after-free in Asterisk PJSIP TCP/SDP handling when TCP connection closes during SDP processing
published 4mo ago modified 9d ago also EUVD-2026-110076 , GHSA-g8q2-p36q-94f6
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository asterisk/asterisk. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
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, an authenticated attacker may cause a heap-use-after-free in `PJSIP TCP/SDP` handling by sending a `SIP INVITE` over a connection-oriented transport and disconnecting before Asterisk responds with the `200 OK`. So far, the crash has only been reproduced when Asterisk is built with `Address Sanitizer`, which detects the issue. `Address Sanitizer` is a development tool with significant performance overhead and, according to the maintainer, is not used in production systems. 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.
Patch / fix
- asterisk open_source 20.20.1, 21.12.3, 22.10.1, 23.4.1
- digium certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
- sangoma certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
- asterisk certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
- digium asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1
- asterisk Debian 14 1:22.10.1+dfsg+~cs6.17.60671434-1
debian advisories DEBIAN-CVE-2026-57187
- github.com/asterisk/asterisk@0f07616 commit
- github.com/asterisk/asterisk@27b9544 commit
- github.com/asterisk/asterisk@6e1f4df commit
- github.com/asterisk/asterisk@9e0386c commit
- github.com/asterisk/asterisk@b7ba854 commit
- github.com/asterisk/asterisk@d4e3000 commit
- github.com/asterisk/asterisk@f1e4762 commit
- github.com/asterisk/asterisk/releases/tag/20.20.1 release
- github.com/asterisk/asterisk/releases/tag/21.12.3 release
- github.com/asterisk/asterisk/releases/tag/22.10.1 release
Is CVE-2026-57187 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-57187 updated cvss 6.5
asterisk: Asterisk: Denial of Service via premature disconnect during SIP INVITE handling
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 9d ago
Exploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/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:X |
Affected products
- asterisk asterisk
- asterisk certified-asterisk
Classification
References
- github.com /asterisk/asterisk/commit/0f076168e0be31ebee37762192d0ee049e9c0d42
- github.com /asterisk/asterisk/commit/27b9544b32f059a4f614169243eaa7559f622aa0
- github.com /asterisk/asterisk/commit/6e1f4df744369d66ea6f412e355d819b2a7bf26c
- github.com /asterisk/asterisk/commit/9e0386c6d259f0c7499d52499d9891bee8a494fa
- github.com /asterisk/asterisk/commit/b7ba85458796ef54b471017287c7806095dbda76
- github.com /asterisk/asterisk/commit/d4e30005940f86942745bcc64f34748d69870247
- github.com /asterisk/asterisk/commit/f1e47621472bb3d8ad71f32823f5ca986e008437
-
github.com
/asterisk/asterisk/security/advisories/GHSA-g8q2-p36q-94f6
advisory
- github.com /asterisk/asterisk/releases/tag/20.20.1
- github.com /asterisk/asterisk/releases/tag/21.12.3
- github.com /asterisk/asterisk/releases/tag/22.10.1
- github.com /asterisk/asterisk/releases/tag/23.4.1
- github.com /asterisk/asterisk/releases/tag/certified-20.7-cert11
- github.com /asterisk/asterisk/releases/tag/certified-22.8-cert3
- github.com /asterisk/asterisk/tree/24.0.0-pre1
Sources
- CVE List CVE-2026-57187
- NVD CVE-2026-57187
- Maintainer advisory GHSA-g8q2-p36q-94f6
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of asterisk/asterisk published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.