SIPGO is a library for writing SIP services in the GO language. Prior to 1.4.3, WSConnection.Read in sip/transport_ws.go creates a wsutil.Reader without setting MaxFrameSize, allowing NextFrame to accept a client-controlled header.Length before ParseMaxMessageLength is applied. An unauthenticated WS or WSS peer can send a frame header declaring an extremely large payload, causing an oversized allocation or a makeslice length panic before the payload is read and crashing or exhausting memory in the server process. This issue is fixed in version 1.4.3.
CVE-2026-77322
HIGHPre-NVD 7.57.5—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. 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, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 48%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 23, 2026
Advisory Details (3)
Auto-updated Sep 22, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available
v1.4.3
Patch available: emiago/sipgo v1.4.3
https://github.com/emiago/sipgo/releases/tag/v1.4.3github_commit Patch Available
commit 769e4bc95837 (emiago/sipgo)
Patch available: emiago/sipgo v1.4.3 (contains commit 769e4bc95837)
https://github.com/emiago/sipgo/commit/769e4bc958376e2363566c8f7042202b410becdcgithub Patch Available🟡 PoC Available
DoS via unvalidated WebSocket frame length · Advisory · emiago/sipgo · GitHub
https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75whVendor Advisories for CVE-2026-77322(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/emiago/sipgo | — | 1.4.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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-09-23 18:25 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 15:20 UTCEG score recompute
- 2026-09-23 15:15 UTCEG score recompute
- 2026-09-22 20:32 UTCEG score recompute
- 2026-09-22 19:58 UTCEG score recompute
- 2026-09-22 19:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-77322?
CVE-2026-77322 is a high vulnerability published on September 22, 2026. SIPGO is a library for writing SIP services in the GO language. Prior to 1.4.3, WSConnection.Read in sip/transport_ws.go creates a wsutil.Reader without setting MaxFrameSize, allowing NextFrame to accept a client-controlled header.Length before ParseMaxMessageLength is applied. An unauthenticated…
When was CVE-2026-77322 disclosed?
CVE-2026-77322 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77322 actively exploited?
CVE-2026-77322 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.1% of all scored CVEs.
What is the CVSS score of CVE-2026-77322?
CVE-2026-77322 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-77322?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77322, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77322
Is Your Infrastructure Affected by CVE-2026-77322?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.