CVE-2026-77322

{"id": "CVE-2026-77322", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-77322", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-09-23T15:07:56.457117Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "emiago", "product": "sipgo", "versions": [{"status": "affected", "version": "< 1.4.3"}]}]}], "published": "2026-09-22T20:17:08.200", "references": [{"url": "https://github.com/emiago/sipgo/commit/769e4bc958376e2363566c8f7042202b410becdc", "source": "security-advisories@github.com"}, {"url": "https://github.com/emiago/sipgo/releases/tag/v1.4.3", "source": "security-advisories@github.com"}, {"url": "https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh", "source": "security-advisories@github.com"}, {"url": "https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-789"}]}], "descriptions": [{"lang": "en", "value": "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."}], "lastModified": "2026-09-23T18:12:04.247", "sourceIdentifier": "security-advisories@github.com"}