# 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.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 17 Dec 2025
- **Also known as:** GHSA-c623-f998-8hhv, GO-2025-4244, MINI-82hj-w225-qw8m, MINI-rqv5-32rf-hf7g

## 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.

Weakness: CWE-755 (Improper Handling of Exceptional Conditions), CWE-476 (NULL Pointer Dereference)

## 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 | Ecosystem | 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: 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68274 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68274 exists.

Affected packages and fixed versions:
- github.com/emiago/sipgo (Go): affected all versions; fixed in 1.0.0-alpha-1
- github.com/emiago/sipgo (Go): affected from 0.3.0; fixed in 1.0.0-alpha-1
- github.com/emiago/sipgo (Go): affected from 0.3.0; fixed in 1.0.0-alpha-1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68274/ (Markdown: https://insights.sbomify.com/CVE-2025-68274/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68274
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68274
- OSV: https://osv.dev/vulnerability/CVE-2025-68274

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68274/
Summaries are generated and may contain mistakes; the official description above is the record.