{"api_version":"1","generated_at":"2026-10-27T09:43:08+00:00","cve":"CVE-2026-77322","urls":{"html":"https://cve.report/CVE-2026-77322","api":"https://cve.report/api/cve/CVE-2026-77322.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-77322","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-77322"},"summary":{"title":"SIPGO: DoS via unvalidated WebSocket frame length","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.","state":"PUBLISHED","assigner":"GitHub_M","published_at":"2026-09-22 20:17:08","updated_at":"2026-09-23 18:12:04"},"problem_types":["CWE-789","CWE-789 CWE-789: Memory Allocation with Excessive Size Value"],"metrics":[{"version":"3.1","source":"security-advisories@github.com","type":"Secondary","score":"7.5","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.5","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","data":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":7.5,"baseSeverity":"HIGH","confidentialityImpact":"NONE","integrityImpact":"NONE","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}}],"references":[{"url":"https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh","name":"https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh","refsource":"134c704f-9b21-4f2e-91b3-4a467353bcc0","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/emiago/sipgo/commit/769e4bc958376e2363566c8f7042202b410becdc","name":"https://github.com/emiago/sipgo/commit/769e4bc958376e2363566c8f7042202b410becdc","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/emiago/sipgo/releases/tag/v1.4.3","name":"https://github.com/emiago/sipgo/releases/tag/v1.4.3","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-77322","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-77322","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"emiago","product":"sipgo","version":"affected < 1.4.3","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"77322","cve":"CVE-2026-77322","epss":"0.005240000","percentile":"0.419550000","score_date":"2026-09-24","updated_at":"2026-09-25 00:02:55"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-77322","options":[{"Exploitation":"poc"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-09-23T15:07:56.457117Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-09-23T15:08:21.990Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"references":[{"tags":["exploit"],"url":"https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh"}],"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"product":"sipgo","vendor":"emiago","versions":[{"status":"affected","version":"< 1.4.3"}]}],"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."}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":7.5,"baseSeverity":"HIGH","confidentialityImpact":"NONE","integrityImpact":"NONE","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-789","description":"CWE-789: Memory Allocation with Excessive Size Value","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-09-22T19:52:12.441Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"name":"https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh","tags":["x_refsource_CONFIRM"],"url":"https://github.com/emiago/sipgo/security/advisories/GHSA-8h6x-h86x-75wh"},{"name":"https://github.com/emiago/sipgo/commit/769e4bc958376e2363566c8f7042202b410becdc","tags":["x_refsource_MISC"],"url":"https://github.com/emiago/sipgo/commit/769e4bc958376e2363566c8f7042202b410becdc"},{"name":"https://github.com/emiago/sipgo/releases/tag/v1.4.3","tags":["x_refsource_MISC"],"url":"https://github.com/emiago/sipgo/releases/tag/v1.4.3"}],"source":{"advisory":"GHSA-8h6x-h86x-75wh","discovery":"UNKNOWN"},"title":"SIPGO: DoS via unvalidated WebSocket frame length"}},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2026-77322","datePublished":"2026-09-22T19:52:12.441Z","dateReserved":"2026-08-20T19:24:11.617Z","dateUpdated":"2026-09-23T15:08:21.990Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-22 20:17:08","lastModifiedDate":"2026-09-23 18:12:04","problem_types":["CWE-789","CWE-789 CWE-789: Memory Allocation with Excessive Size Value"],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"NONE","availabilityImpact":"HIGH"},"exploitabilityScore":3.9,"impactScore":3.6}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-09-23T15:07:56.457117Z","id":"CVE-2026-77322","options":[{"exploitation":"poc"},{"automatable":"yes"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"77322","Ordinal":"1","Title":"SIPGO: DoS via unvalidated WebSocket frame length","CVE":"CVE-2026-77322","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"77322","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"SIPGO: DoS via unvalidated WebSocket frame length"}]}}}