Vulnerability 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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/emiago/sipgo/commit/769e4bc958376e2363566c8f7042202b410becdc
- https://github.com/emiago/sipgo/releases/tag/v1.4.3
- https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh
- https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh
FAQ
What is CVE-2026-77322?
CVE-2026-77322 is a vulnerability with a CVSS score of 7.5 (HIGH). 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 acc...
How severe is CVE-2026-77322?
CVE-2026-77322 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-77322?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.