Homepage

Uncontrolled Memory Allocation Affecting livekit-sip-fips package, versions <1.14.0-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.52% (42nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-LIVEKITSIPFIPS-20067899
  • published24 Sept 2026
  • disclosed22 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 22 Sep 2026

NewCVE-2026-77322  (opens in a new tab)
CWE-789  (opens in a new tab)

How to fix?

Upgrade Minimos:latest livekit-sip-fips to version 1.14.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream livekit-sip-fips package and not the livekit-sip-fips package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.