Live › vulnerability › CVE-2026-77322
Go to dashboardsipgo is a Go library for building SIP servers, and before 1.4.3 its WebSocket transport reads frames without a size limit. An unauthenticated remote peer can send one frame header declaring a huge payload, which crashes the process or exhausts its memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| github.com/emiago/sipgo | go | < 1.4.3 | 1.4.3 |
Run go list -m github.com/emiago/sipgo in each service and check whether the version is below 1.4.3.
Search the codebase for sipgo transport usage over WS or WSS.
Upgrade github.com/emiago/sipgo to 1.4.3 or later and rebuild.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-77322")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.