SIPGO is a library for writing SIP services in the GO language. Prior to 1.4.1, ParserStream.parseSingle in sip/parser_stream.go allocates a SIP body buffer from the client-controlled Content-Length header before ParseMaxMessageLength is enforced. An unauthenticated peer can send a stream-transport message over TCP, TLS, WS, or WSS with an oversized declared length, causing excessive memory allocation and denial of service before the body is read. This issue is fixed in version 1.4.1.
CVE-2026-58268
HIGHPre-NVD 7.57.5—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 48%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 23, 2026
Advisory Details (3)
Auto-updated Sep 22, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available
v1.4.1
Patch available: emiago/sipgo v1.4.1
https://github.com/emiago/sipgo/releases/tag/v1.4.1github_commit Patch Available
commit a7be60a07f48 (emiago/sipgo)
Patch available: emiago/sipgo v1.4.1 (contains commit a7be60a07f48)
https://github.com/emiago/sipgo/commit/a7be60a07f48c06b3cdd5a7d35eb820b3df5736cgithub Patch Available🟡 PoC Available
DoS via unvalidated Content-Length in the stream parser · Advisory · emiago/sipgo · GitHub
https://github.com/emiago/sipgo/security/advisories/GHSA-pg59-5vwg-4jxqVendor Advisories for CVE-2026-58268(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/emiago/sipgo | — | 1.4.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 18:25 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 13:18 UTCEG score recompute
- 2026-09-23 12:46 UTCEG score recompute
- 2026-09-22 20:32 UTCEG score recompute
- 2026-09-22 19:53 UTCEG score recompute
- 2026-09-22 19:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-58268?
CVE-2026-58268 is a high vulnerability published on September 22, 2026. SIPGO is a library for writing SIP services in the GO language. Prior to 1.4.1, ParserStream.parseSingle in sip/parser_stream.go allocates a SIP body buffer from the client-controlled Content-Length header before ParseMaxMessageLength is enforced. An unauthenticated peer can send a stream-transport…
When was CVE-2026-58268 disclosed?
CVE-2026-58268 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58268 actively exploited?
CVE-2026-58268 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.1% of all scored CVEs.
What is the CVSS score of CVE-2026-58268?
CVE-2026-58268 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-58268?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58268, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58268
Is Your Infrastructure Affected by CVE-2026-58268?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.