CVE-2025-68274: emiago sipgo · NULL Pointer Dereference
Affects emiago sipgoSource CVE Database V5
Not known to be exploited · CVSS 8.7 High · fixed in 1.0.0 : patch emiago sipgo soon.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Gogithub.com/emiago/sipgopkg:golang/github.com/emiago/sipgoOther threats | Affected– | Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade all SIPGO library instances to version 1.0.0-alpha-1 or later, where the NULL pointer dereference issue is patched. 2. Implement strict input validation on SIP requests at the network perimeter or SIP proxy level to reject malformed SIP messages lacking mandatory headers such as the To header. 3. Deploy SIP-aware intrusion detection and prevention systems (IDS/IPS) that can detect and block anomalous SIP traffic patterns indicative of malformed requests. 4. Conduct regular code audits and fuzz testing on SIP handling components to identify and remediate similar vulnerabilities proactively. 5. Establish robust monitoring and alerting for SIP service crashes or abnormal restarts to enable rapid incident response. 6. Consider deploying SIP redundancy and failover mechanisms to maintain service availability during potential attack attempts. 7. Engage with vendors and open-source communities to stay informed about updates and patches related to SIPGO and related SIP libraries. 8. For organizations unable to upgrade immediately, implement application-level wrappers or middleware that perform header validation before passing requests to SIPGO functions.
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.