SIPGO Security Update Addresses 2 Vulnerabilities
Tech GuruQuick Answer
SIPGO 1.4.3 is the combined fix for two unauthenticated denial-of-service flaws. Version 1.4.1 bounds allocation from SIP Content-Length on stream transports; 1.4.3 also fixes allocation from WebSocket frame length. A downstream SIP message-size limit does not protect an earlier WebSocket buffer allocation.
Confirm Scope And Apply The Supported Fix
What to do now: Identify services embedding SIPGO and their TCP, TLS, WS or WSS listeners. Update the Go dependency to 1.4.3, rebuild the application and verify the deployed binary.
Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | SIPGO packages and release streams identified in the project advisories |
|---|---|
| Advisory | GHSA-pg59-5vwg-4jxq / GHSA-8h6x-h86x-75wh |
| CVEs | CVE-2026-58268, CVE-2026-77322 |
| Project advisory publication | 2026-06-30 and 2026-07-04 (two project advisories) |
| Recorded source timestamp (historical snapshot) | 2026-09-22 20:34:31 UTC |
| Affected versions | github.com/emiago/sipgo <= 1.4.0; github.com/emiago/sipgo <= 1.4.2 |
| Fixed version | 1.4.1 fixes CVE-2026-58268; 1.4.3 fixes CVE-2026-77322 and is the combined target. |
| CVSS base score | 7.5 (CVSS v3) |
| CVSS severity | High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
CVE-2026-58268 affects stream parsing through 1.4.0: the declared body length is used before the message-size check, allowing memory exhaustion on TCP/TLS/WS/WSS. CVE-2026-77322 affects WS/WSS through 1.4.2: an unchecked frame length can trigger an excessive allocation or a process-ending slice-size panic before payload validation.
What To Validate Now
- Inventory. Locate SIPGO packages and release streams identified in the project advisories deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: github.com/emiago/sipgo <= 1.4.0; github.com/emiago/sipgo <= 1.4.2 Do not infer applicability from product family or severity alone.
- Remediate. Update affected application builds to SIPGO 1.4.3. A standalone module-cache update or stopping at 1.4.1 does not establish that deployed WS/WSS services contain both fixes.
- Validate. In a resource-limited test deployment, verify normal SIP traffic and bounded rejection of oversized body/frame declarations for enabled transports. Do not send memory-exhaustion payloads to live call-processing services.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
