Description
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.
Published: 2026-09-22
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service
Action: Immediate Patch
AI Analysis

Impact

The vulnerability resides in the WebSocket handling code of the SIPGO library, where the maximum frame size is not bounded before reading a message header. An attacker can send a frame header with an excessively large payload size, causing the library to allocate an oversized buffer or trigger a makeslice panic. This results in a crash or out‑of‑memory condition in the server process, leading to a denial of service. The weakness is an unbounded memory allocation, classified as CWE‑789.

Affected Systems

The issue affects the sipgo library from emiago. Versions prior to 1.4.3 are vulnerable; the fix appears in release 1.4.3 and later.

Risk and Exploitability

The CVSS score is 7.5, indicating a high severity. Exploitation requires only the ability to connect to the WebSocket or WSS endpoint, and no authentication is required. The EPSS score is not available, and the vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog, but the straightforward nature of the attack and the lack of controls suggest a significant risk to exposed services.

Generated by OpenCVE AI on September 22, 2026 at 21:30 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade sipgo to version 1.4.3 or later.
  • If an upgrade cannot be performed immediately, restrict WebSocket connections to trusted hosts or ports using network filtering and monitor for abnormal frame sizes.
  • As a temporary code-level fix, configure the wsutil.Reader with an appropriate MaxFrameSize before calling NextFrame, or modify the library to enforce a safe maximum frame size.

Generated by OpenCVE AI on September 22, 2026 at 21:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-8h6x-h86x-75wh SIPGO: DoS via unvalidated WebSocket frame length
History

Wed, 23 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 22 Sep 2026 22:30:00 +0000

Type Values Removed Values Added
First Time appeared Emiago
Emiago sipgo
Vendors & Products Emiago
Emiago sipgo

Tue, 22 Sep 2026 20:00:00 +0000

Type Values Removed Values Added
Description 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.
Title SIPGO: DoS via unvalidated WebSocket frame length
Weaknesses CWE-789
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-23T15:08:21.990Z

Reserved: 2026-08-20T19:24:11.617Z

Link: CVE-2026-77322

cve-icon Vulnrichment

Updated: 2026-09-23T15:08:16.479Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-22T20:17:08.200

Modified: 2026-09-23T18:12:04.247

Link: CVE-2026-77322

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-22T22:15:06Z

Weaknesses
  • CWE-789

    Memory Allocation with Excessive Size Value