{"id":"CVE-2026-45084","title":"OpenSIPS is a Session Initiation Protocol (SIP) server implementation","summary":"OpenSIPS is a Session Initiation Protocol (SIP) server implementation. Versions 3.4.0 through 3.6.5 contain a denial of service vulnerability in the presence module. When the presence module's handle_publish() function processes a SIP PU…","severity":"none","cwe":["CWE-476"],"published":"2026-08-04","updated":"2026-09-08","sourceUpdated":"2026-09-08T20:41:31.497","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-45084","references":[{"url":"https://github.com/OpenSIPS/opensips/security/advisories/GHSA-h3ww-hchh-x2g9","label":"security-advisories@github.com"},{"url":"https://github.com/OpenSIPS/opensips/security/advisories/GHSA-h3ww-hchh-x2g9","label":"134c704f-9b21-4f2e-91b3-4a467353bcc0"}],"tags":["nvd"],"epss":0.00465,"epssPercentile":0.39469,"ingestedAt":"2026-09-08T21:11:12.266Z","slug":"CVE-2026-45084","body":"## Overview\n\nOpenSIPS is a Session Initiation Protocol (SIP) server implementation. Versions 3.4.0 through 3.6.5 contain a denial of service vulnerability in the presence module. When the presence module's handle_publish() function processes a SIP PUBLISH request with an Event: presence header and a message body while the configuration option enable_sphere_check=1 is set, it invokes the get_content_type() macro without first calling parse_content_type_hdr(), causing it to dereference uninitialized or NULL Content-Type parsing state and crash. If a Content-Type header is present but unparsed, msg->content_type->parsed is NULL and is dereferenced as a content_t pointer; if the request lacks a Content-Type header entirely, msg->content_type itself is NULL, and both cases lead to a crash. A remote attacker can therefore cause a denial of service against an affected instance with a single PUBLISH request over UDP or TCP, using either a valid Content-Type: application/pidf+xml request or one with the header removed, and the vulnerable code path itself does not enforce authentication (though a deployment's routing configuration may require it before this route is reached). The issue has been fixed in version 3.6.6 and 4.0.0-rc1.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}