UBUNTU-CVE-2026-45084 (CVE-2026-45084)
Vulnerability from osv_ubuntu – Published: 2026-08-04 22:17 – Updated: 2026-08-04 22:17 – Source websiteOpenSIPS 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.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "opensips",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-b2bua-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-berkeley-bin",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-berkeley-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-carrierroute-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-compression-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-console",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-cpl-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-dbhttp-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-dialplan-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-emergency-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-geoip-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-http-modules",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-identity-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-jabber-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-json-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-ldap-modules",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-lua-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-memcached-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-mysql-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-perl-modules",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-postgres-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-presence-modules",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-rabbitmq-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-radius-modules",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-redis-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-regex-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-restclient-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-sctp-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-snmpstats-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-sqlite-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-tls-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-tlsmgm-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-unixodbc-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-wss-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-xmlrpc-module",
"binary_version": "2.2.2-3build4"
},
{
"binary_name": "opensips-xmpp-module",
"binary_version": "2.2.2-3build4"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "opensips",
"purl": "pkg:deb/ubuntu/opensips@2.2.2-3build4?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.2.2-3build2",
"2.2.2-3build3",
"2.2.2-3build4"
]
}
],
"aliases": [],
"details": "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\u0027s 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-\u003econtent_type-\u003eparsed is NULL and is dereferenced as a content_t pointer; if the request lacks a Content-Type header entirely, msg-\u003econtent_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\u0027s 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.",
"id": "UBUNTU-CVE-2026-45084",
"modified": "2026-08-04T22:17:00Z",
"published": "2026-08-04T22:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-45084"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45084"
},
{
"type": "REPORT",
"url": "https://github.com/OpenSIPS/opensips/security/advisories/GHSA-h3ww-hchh-x2g9"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "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",
"type": "CVSS_V4"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-45084"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.