SIPGO: DoS via unvalidated WebSocket frame length

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-77322: 0.61% estimated exploitation activity in the next 30 days; percentile 49.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The WebSocket transport allocates a buffer from the frame payload length before validating its size, which can lead to an unauthenticated DoS. Details WSConnection.Read allocates a buffer from the declared WebSocket frame length before reading the payload (https://github.com/emiago/sipgo/blob/v1.4.0/sip/transportws.go#L400): - NextFrame() reads only the frame header and never checks the length: wsutil.NewReader is created with no MaxFrameSize (0 = unlimited). ParseMaxMessageLength applies only downstream, not here. - A value above the max slice size (e.g. 2^63-1) panics make. sipgo does not recover from this panic, so it crashes the whole server process. PoC Tested on emiago/sipgo v1.4.0 (latest). After a normal WebSocket handshake, send one masked text frame consisting of the header only (no payload), declaring a huge length. The allocation runs as soon as the header is read. This crashes the server process: Suggested Fix Set MaxFrameSize on the wsutil.NewReader. Impact…

Published by the source

22 Sep 2026, 20:34 UTC

Last modified by the source

1 Oct 2026, 20:45 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8h6x-h86x-75wh

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6559

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8h6x-h86x-75wh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-77322

Advisory: SIPGO: DoS via unvalidated WebSocket frame length
IDs: CVE-2026-77322, GHSA-8h6x-h86x-75wh
Record: https://patchnext.com/advisories/cve-2026-77322 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/emiago/sipgo 1.4.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/emiago/sipgo: affected <= 1.4.2; fixed in 1.4.3

## Suggested inspection (read-only)
- Go github.com/emiago/sipgo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/emiago/sipgo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8h6x-h86x-75wh (OSV record GHSA-8h6x-h86x-75wh lists affected ranges: Go github.com/emiago/sipgo >=0 <1.4.3 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6559 (OSV record GO-2026-6559 lists affected ranges: Go github.com/emiago/sipgo >=0 <1.4.3 (fixed))
- Verified: https://github.com/advisories/GHSA-8h6x-h86x-75wh (GitHub-reviewed advisory GHSA-8h6x-h86x-75wh lists affected ranges: Go github.com/emiago/sipgo >=0 <=1.4.2)

Commands are suggestions: review each one before running it.