PJSIP is a free and open source multimedia communication library written in C. Prior to commit a1b707c, a stack buffer overflow exists in the SRTP/SDES media transport when processing a=crypto attributes during SDP offer/answer (sdes_encode_sdp() in transport_srtp_sdes.c). This affects applications with SRTP enabled (use_srtp optional or mandatory, using SDES keying). During media negotiation, the crypto attributes from the remote SDP are collected into a fixed-size array without bounding their number; a remote peer that includes an excessive number of a=crypto attributes in a single media description can write past the end of that array on the stack. This is reachable from an incoming SIP INVITE during offer/answer, before application-level authentication. Impact may range from unexpected application termination to control flow hijack/memory corruption. Applications that do not enable SRTP are not affected. This issue has been patched via commit a1b707c.
CVE-2026-57162
This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).
- CVSS v3
- 9.1
- EG Score
- 9.1CRITICALmedium confidence
- EG Risk
- 56EG Risk 56/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation1% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation. - EPSS PROB
- 0.6%
- EPSS %ILE
- 49th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 4, 2026
Last Modified
September 11, 2026
Advisory Details (2)
Auto-updated Sep 15, 2026Stack overflow parsing SDP a=crypto attributes · Advisory · pjsip/pjproject · GitHub
https://github.com/pjsip/pjproject/security/advisories/GHSA-m9g3-jcj8-qjfmcommit a1b707c0c9b0 (pjsip/pjproject)
Fix landed in pjsip/pjproject commit a1b707c0c9b0 — awaiting tagged release
https://github.com/pjsip/pjproject/commit/a1b707c0c9b0506faf2a8a438b60f11ffd6a6fd9Affected Packages
(1 across 1 ecosystem)
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| asterisk | 0.1.11-3 ... 1:22.9.0+dfsg+~cs6.16.60671434-1 (296 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 56× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-09 23:05 UTCEG score recompute
- 2026-10-09 20:07 UTCEPSS rescore
- 2026-10-09 01:09 UTCEG score recompute
- 2026-10-08 17:13 UTCEPSS rescore
- 2026-10-08 02:51 UTCEG score recompute
- 2026-10-07 23:48 UTCEPSS rescore
- 2026-10-06 16:24 UTCEG score recompute
- 2026-10-06 15:18 UTCEPSS rescore
- 2026-10-05 20:28 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescore
- 2026-10-04 23:33 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-03 16:19 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 21:32 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-02 00:30 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 15:26 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-30 02:40 UTCEG score recompute
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-28 23:02 UTCEG score recompute
- 2026-09-28 15:13 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescore
Show 44 moreShow fewer
- 2026-09-27 16:37 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 17:05 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-26 02:09 UTCEG score recompute
- 2026-09-24 15:19 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 20:19 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 17:56 UTCEG score recompute
- 2026-09-21 22:39 UTCEG score recompute
- 2026-09-20 23:48 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 17:35 UTCEG score recompute
- 2026-09-18 22:43 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:22 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 18:23 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:49 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:18 UTCEG score recompute
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 17:14 UTCEG score recompute
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 18:37 UTCEG score recompute
- 2026-09-11 15:53 UTCEG score recompute▲ 0.30
- 2026-09-11 15:53 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 10:45 UTCEG score recompute
- 2026-09-10 11:12 UTCEG score recompute
- 2026-09-10 09:35 UTCEPSS rescore
- 2026-09-09 09:35 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 16:48 UTCEG score recompute
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 17:24 UTCEG score recompute
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 18:00 UTCEG score recompute
- 2026-09-04 18:35 UTCEG score recompute
- 2026-09-04 17:35 UTCEG score recompute
- 2026-09-04 17:20 UTCEG score recompute
- 2026-09-04 17:19 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:14:asterisk
Frequently asked(5)
What is CVE-2026-57162?
When was CVE-2026-57162 disclosed?
Is CVE-2026-57162 actively exploited?
What is the CVSS score of CVE-2026-57162?
How do I remediate CVE-2026-57162?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57162
Is Your Infrastructure Affected by CVE-2026-57162?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.