CVE-2026-57163

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.4% (32nd 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

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).

PJSIP is a free and open source multimedia communication library written in C. Prior to commit c4a151a, a stack buffer overflow exists in the GnuTLS TLS backend when parsing the Subject Alternative Name extension of a peer certificate (tls_cert_get_info() in ssl_sock_gtls.c). Only GnuTLS builds are affected (--with-gnutls); OpenSSL and Apple SecureTransport/Network.framework builds are not affected. While extracting certificate information after a TLS handshake, an incorrect buffer-size value can cause an oversized SubjectAltName entry to be written past the end of a fixed-size stack buffer. A network-positioned attacker presenting a crafted certificate — a malicious server to a connecting client, or a malicious client to a server that requests certificates — can trigger this during the TLS handshake, before any SIP-level authentication. Impact may range from unexpected application termination to control flow hijack/memory corruption. This issue has been patched via commit c4a151a.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG 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 computed
Severity91% × 45%
Exploitation0% × 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.4%
EPSS %ILE
32nd
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 partial (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, 2026
Fix referenced — no release confirmed yet. Sources: github_commit, github.
githubMentions a patch (unverified)

Stack overflow parsing a TLS peer certificate's SubjectAltName in GnuTLS backend · Advisory · pjsip/pjproject · GitHub

https://github.com/pjsip/pjproject/security/advisories/GHSA-jm2j-6rg6-qvwx
github_commit

commit c4a151af86fa (pjsip/pjproject)

Fix landed in pjsip/pjproject commit c4a151af86fa — awaiting tagged release

https://github.com/pjsip/pjproject/commit/c4a151af86fadd16d9480b2603eeb2abf4fb4f78

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
asterisk0.1.11-3 ... 1:22.9.0+dfsg+~cs6.16.60671434-1 (296 versions)
  • every version on: no fix on record
—

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.

  1. 2026-10-09 23:05 UTCEG score recompute
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-09 01:09 UTCEG score recompute
  4. 2026-10-08 17:13 UTCEPSS rescore
  5. 2026-10-08 03:01 UTCEG score recompute
  6. 2026-10-07 23:48 UTCEPSS rescore
  7. 2026-10-06 19:08 UTCEG score recompute
  8. 2026-10-06 15:18 UTCEPSS rescore
  9. 2026-10-05 22:59 UTCEG score recompute
  10. 2026-10-05 17:43 UTCEPSS rescore
  11. 2026-10-05 01:13 UTCEG score recompute
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-03 16:28 UTCEG score recompute
  14. 2026-10-03 14:26 UTCEPSS rescore
  15. 2026-10-02 21:49 UTCEG score recompute
  16. 2026-10-02 17:56 UTCEPSS rescore
  17. 2026-10-01 21:26 UTCEG score recompute
  18. 2026-10-01 19:50 UTCEPSS rescore
  19. 2026-09-30 15:26 UTCEG score recompute
  20. 2026-09-30 15:03 UTCEPSS rescore
  21. 2026-09-30 02:40 UTCEG score recompute
  22. 2026-09-29 15:22 UTCEPSS rescore
  23. 2026-09-29 00:44 UTCEG score recompute
  24. 2026-09-28 16:52 UTCEG score recompute
  25. 2026-09-28 13:51 UTCEPSS rescore
Show 44 more
  1. 2026-09-27 17:09 UTCEG score recompute
  2. 2026-09-27 13:48 UTCEPSS rescore
  3. 2026-09-26 17:05 UTCEG score recompute
  4. 2026-09-26 15:59 UTCEPSS rescore
  5. 2026-09-26 02:09 UTCEG score recompute
  6. 2026-09-24 16:26 UTCEG score recompute
  7. 2026-09-24 14:04 UTCEPSS rescore
  8. 2026-09-23 20:49 UTCEG score recompute
  9. 2026-09-23 17:54 UTCEPSS rescore
  10. 2026-09-22 17:19 UTCEG score recompute
  11. 2026-09-22 01:00 UTCEG score recompute
  12. 2026-09-20 20:34 UTCEG score recompute
  13. 2026-09-20 20:16 UTCEPSS rescore
  14. 2026-09-19 17:03 UTCEG score recompute
  15. 2026-09-18 21:22 UTCEG score recompute
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-17 20:22 UTCEG score recompute
  18. 2026-09-17 19:31 UTCEPSS rescore
  19. 2026-09-16 15:07 UTCEG score recompute
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 07:15 UTCEG score recompute
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-15 06:41 UTCEG score recompute
  24. 2026-09-15 03:11 UTCEPSS rescore
  25. 2026-09-13 19:19 UTCEG score recompute
  26. 2026-09-13 16:47 UTCEPSS rescore
  27. 2026-09-12 15:48 UTCEG score recompute
  28. 2026-09-11 15:53 UTCEG score recompute▲ 0.30
  29. 2026-09-11 15:53 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  30. 2026-09-11 14:53 UTCEPSS rescore
  31. 2026-09-11 10:47 UTCEG score recompute
  32. 2026-09-10 11:12 UTCEG score recompute
  33. 2026-09-10 09:35 UTCEPSS rescore
  34. 2026-09-09 09:41 UTCEG score recompute
  35. 2026-09-08 22:01 UTCEPSS rescore
  36. 2026-09-07 17:22 UTCEG score recompute
  37. 2026-09-07 16:01 UTCEPSS rescore
  38. 2026-09-06 17:48 UTCEG score recompute
  39. 2026-09-06 13:47 UTCEPSS rescore
  40. 2026-09-05 18:13 UTCEG score recompute
  41. 2026-09-04 18:34 UTCEG score recompute
  42. 2026-09-04 17:35 UTCEG score recompute
  43. 2026-09-04 17:20 UTCEG score recompute
  44. 2026-09-04 17:19 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-57163?
CVE-2026-57163 is a critical vulnerability published on September 4, 2026. PJSIP is a free and open source multimedia communication library written in C. Prior to commit c4a151a, a stack buffer overflow exists in the GnuTLS TLS backend when parsing the Subject Alternative Name extension of a peer certificate (tlscertgetinfo() in sslsock_gtls.c). Only GnuTLS builds are…
When was CVE-2026-57163 disclosed?
CVE-2026-57163 was first published on September 4, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57163 actively exploited?
CVE-2026-57163 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57163?
CVE-2026-57163 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-57163?
A fix for CVE-2026-57163 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57163

Explore →

Is Your Infrastructure Affected by CVE-2026-57163?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs