Skip to main content
VulnerabilityPublished

CVE-2026-77322: emiago sipgo · Excessive Memory Allocation

Affects emiago sipgoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.4.3 soon.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade sipgo and github.com/emiago/sipgo to 1.4.3.

Affected software

ProductAffectedFixed in
emiagosipgoAffected
  • <1.4.3
Fixed in
  • 1.4.3
Gogithub.com/emiago/sipgopkg:golang/github.com/emiago/sipgoOther threatsAffected
  • <1.4.3
Fixed in
  • 1.4.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to emiago sipgo version 1.4.3 or later, where this issue is fixed by properly setting MaxFrameSize in WSConnection.Read. No other mitigations are specified. Patch status is confirmed as fixed in version 1.4.3.

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.

References

Community reviews

Loading reviews…