Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
SIPGO versions before 1.4.1 are vulnerable to a denial-of-service attack through the stream parser, which allocates the SIP body buffer from the Content-Length header before checking its size. An unauthenticated remote attacker who can send SIP messages over a stream transport (TCP, TLS, WS or WSS) can cause the service to run out of memory. Upgrade to sipgo 1.4.1, which fixes the issue.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0061, the 49th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:12 UTC First seen by agentprime
- 31 Oct 2026, 14:12 UTC Confirmed by OSV