CVE-2026-77322

Published: Sep 22, 2026Modified: Sep 23, 2026

7.5

Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitability: 3.9 / Impact: 3.6

Source: security-advisories@github.com (Secondary)

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.

Related CWEs

CWE-789

Memory Allocation with Excessive Size Value

The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

References (4)

https://github.com/emiago/sipgo/commit/769e4bc958376e2363566c8f7042202b410becdc

Source: security-advisories@github.com

https://github.com/emiago/sipgo/releases/tag/v1.4.3

Source: security-advisories@github.com

https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh

Source: security-advisories@github.com

https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh

Source: 134c704f-9b21-4f2e-91b3-4a467353bcc0

Timeline

No history available yet.