CVE-2025-68274 SIPGO library has response DoS vulnerability via nil pointer dereference
Remote attackers can crash SIP applications using the SIPGO library by sending a malformed request missing the To header, causing a nil pointer dereference.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-68274?
CVE-2025-68274 is a high-severity vulnerability in emiago sipgo, published on 16 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
SIPGO is a library for writing SIP services in the GO language. Starting in version 0.3.0 and prior to version 1.0.0-alpha-1, a nil pointer dereference vulnerability is in the SIPGO library's `NewResponseFromRequest` function that affects all normal SIP operations. The vulnerability allows remote attackers to crash any SIP application by sending a single malformed SIP request without a To header. The vulnerability occurs when SIP message parsing succeeds for a request missing the To header, but the response creation code assumes the To header exists without proper nil checks. This affects routine operations like call setup, authentication, and message handling - not just error cases. This vulnerability affects all SIP applications using the sipgo library, not just specific configurations or edge cases, as long as they make use of the `NewResponseFromRequest` function. Version 1.0.0-alpha-1 contains a patch for the issue.
Which versions are affected by CVE-2025-68274?
3 open source packages ship an affected version, including github.com/emiago/sipgo. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/emiago/sipgo Go | All versions | 1.0.0-alpha-1 |
github.com/emiago/sipgo Go | From 0.3.0 | 1.0.0-alpha-1 |
github.com/emiago/sipgo Go | From 0.3.0 | 1.0.0-alpha-1 |
Products include Emiago Sipgo.
How do I fix CVE-2025-68274?
Upgrade github.com/emiago/sipgo to 1.0.0-alpha-1 or later.
Is CVE-2025-68274 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68274 exists.
Sources
Also known as GHSA-c623-f998-8hhv, GO-2025-4244, MINI-82hj-w225-qw8m, MINI-rqv5-32rf-hf7g.