CVE-2026-45103 (GCVE-0-2026-45103)
Vulnerability from cvelistv5 – Published: 2026-08-04 21:56 – Updated: 2026-08-05 17:55
VLAI
EPSS
VEX
Title
OpenSIPS: SIP Message Smuggling via TCP Content-Length Integer Overflow
Summary
OpenSIPS is a Session Initiation Protocol (SIP) server implementation. In versions prior to 3.6.6 and 4.0.0-rc1, the TCP message framing layer parses the Content-Length header using unsigned int arithmetic with no overflow check. When an attacker sends a Content-Length value that overflows unsigned int (e.g., 4294967296), the framing layer computes a wrapped-around value (e.g., 0) and splits the TCP stream at the wrong boundary, causing the body of the first SIP message to be processed as a separate message and enabling SIP message smuggling. Because Content-Length is parsed in the transport layer before authentication, an unauthenticated, network-based attacker can smuggle arbitrary SIP messages over any TCP-based transport (proto_tcp, proto_tls, proto_ws, proto_wss) on any instance with TCP enabled, with no routing-script preconditions. This allows smuggled messages to bypass front-end SBC/proxy security policies, inherit the connection's authentication context, and evade rate limiting. This issue has been fixed in versions 3.6.6 and 4.0.0-rc1.
Severity
7.5 (High)
SSVC
Exploitation: poc
Automatable: yes
Technical Impact: partial
CISA Coordinator (v2.0.3)
CWE
- CWE-190 - Integer Overflow or Wraparound
Assigner
References
3 references
| URL | Tags |
|---|---|
| https://github.com/OpenSIPS/opensips/security/adv… | x_refsource_CONFIRM |
| https://github.com/OpenSIPS/opensips/commit/4d23613b | x_refsource_MISC |
| https://github.com/OpenSIPS/opensips/commit/5f103eff | x_refsource_MISC |
Impacted products
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-45103",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-08-05T17:53:22.085357Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T17:55:45.043Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "opensips",
"vendor": "OpenSIPS",
"versions": [
{
"status": "affected",
"version": "\u003e= 3.4.0, \u003c 3.6.6"
},
{
"status": "affected",
"version": "\u003e= 4.0.0-beta, \u003c 4.0.0-rc1"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "OpenSIPS is a Session Initiation Protocol (SIP) server implementation. In versions prior to 3.6.6 and 4.0.0-rc1, the TCP message framing layer parses the Content-Length header using unsigned int arithmetic with no overflow check. When an attacker sends a Content-Length value that overflows unsigned int (e.g., 4294967296), the framing layer computes a wrapped-around value (e.g., 0) and splits the TCP stream at the wrong boundary, causing the body of the first SIP message to be processed as a separate message and enabling SIP message smuggling. Because Content-Length is parsed in the transport layer before authentication, an unauthenticated, network-based attacker can smuggle arbitrary SIP messages over any TCP-based transport (proto_tcp, proto_tls, proto_ws, proto_wss) on any instance with TCP enabled, with no routing-script preconditions. This allows smuggled messages to bypass front-end SBC/proxy security policies, inherit the connection\u0027s authentication context, and evade rate limiting. This issue has been fixed in versions 3.6.6 and 4.0.0-rc1."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-190",
"description": "CWE-190: Integer Overflow or Wraparound",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-04T21:56:57.422Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/OpenSIPS/opensips/security/advisories/GHSA-jv35-555v-54jh",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/OpenSIPS/opensips/security/advisories/GHSA-jv35-555v-54jh"
},
{
"name": "https://github.com/OpenSIPS/opensips/commit/4d23613b",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/OpenSIPS/opensips/commit/4d23613b"
},
{
"name": "https://github.com/OpenSIPS/opensips/commit/5f103eff",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/OpenSIPS/opensips/commit/5f103eff"
}
],
"source": {
"advisory": "GHSA-jv35-555v-54jh",
"discovery": "UNKNOWN"
},
"title": "OpenSIPS: SIP Message Smuggling via TCP Content-Length Integer Overflow"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-45103",
"datePublished": "2026-08-04T21:56:57.422Z",
"dateReserved": "2026-05-08T19:27:26.699Z",
"dateUpdated": "2026-08-05T17:55:45.043Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-45103",
"date": "2026-08-09",
"epss": "0.00328",
"percentile": "0.25292"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-45103\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2026-08-04T22:17:14.847\",\"lastModified\":\"2026-08-05T19:17:30.650\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"OpenSIPS is a Session Initiation Protocol (SIP) server implementation. In versions prior to 3.6.6 and 4.0.0-rc1, the TCP message framing layer parses the Content-Length header using unsigned int arithmetic with no overflow check. When an attacker sends a Content-Length value that overflows unsigned int (e.g., 4294967296), the framing layer computes a wrapped-around value (e.g., 0) and splits the TCP stream at the wrong boundary, causing the body of the first SIP message to be processed as a separate message and enabling SIP message smuggling. Because Content-Length is parsed in the transport layer before authentication, an unauthenticated, network-based attacker can smuggle arbitrary SIP messages over any TCP-based transport (proto_tcp, proto_tls, proto_ws, proto_wss) on any instance with TCP enabled, with no routing-script preconditions. This allows smuggled messages to bypass front-end SBC/proxy security policies, inherit the connection\u0027s authentication context, and evade rate limiting. This issue has been fixed in versions 3.6.6 and 4.0.0-rc1.\"}],\"affected\":[{\"source\":\"security-advisories@github.com\",\"affectedData\":[{\"vendor\":\"OpenSIPS\",\"product\":\"opensips\",\"versions\":[{\"version\":\"\u003e= 3.4.0, \u003c 3.6.6\",\"status\":\"affected\"},{\"version\":\"\u003e= 4.0.0-beta, \u003c 4.0.0-rc1\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":3.9,\"impactScore\":3.6}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2026-08-05T17:53:22.085357Z\",\"id\":\"CVE-2026-45103\",\"options\":[{\"exploitation\":\"poc\"},{\"automatable\":\"yes\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-190\"}]}],\"references\":[{\"url\":\"https://github.com/OpenSIPS/opensips/commit/4d23613b\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/OpenSIPS/opensips/commit/5f103eff\",\"source\":\"security-advisories@github.com\"},{\"url\":\"https://github.com/OpenSIPS/opensips/security/advisories/GHSA-jv35-555v-54jh\",\"source\":\"security-advisories@github.com\"}]}}",
"redhat_vex": {
"current_release_date": "2026-08-05T13:31:17+00:00",
"cve": "CVE-2026-45103",
"id": "CVE-2026-45103",
"initial_release_date": "2026-08-04T21:56:57.422000+00:00",
"product_status:known_not_affected": "1",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "opensips: SIP message smuggling via TCP Content-Length integer overflow",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45103.json",
"version": "3"
},
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-45103\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"poc\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-08-05T17:53:22.085357Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-08-05T17:55:27.208Z\"}}], \"cna\": {\"title\": \"OpenSIPS: SIP Message Smuggling via TCP Content-Length Integer Overflow\", \"source\": {\"advisory\": \"GHSA-jv35-555v-54jh\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 7.5, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"NONE\"}}], \"affected\": [{\"vendor\": \"OpenSIPS\", \"product\": \"opensips\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003e= 3.4.0, \u003c 3.6.6\"}, {\"status\": \"affected\", \"version\": \"\u003e= 4.0.0-beta, \u003c 4.0.0-rc1\"}]}], \"references\": [{\"url\": \"https://github.com/OpenSIPS/opensips/security/advisories/GHSA-jv35-555v-54jh\", \"name\": \"https://github.com/OpenSIPS/opensips/security/advisories/GHSA-jv35-555v-54jh\", \"tags\": [\"x_refsource_CONFIRM\"]}, {\"url\": \"https://github.com/OpenSIPS/opensips/commit/4d23613b\", \"name\": \"https://github.com/OpenSIPS/opensips/commit/4d23613b\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://github.com/OpenSIPS/opensips/commit/5f103eff\", \"name\": \"https://github.com/OpenSIPS/opensips/commit/5f103eff\", \"tags\": [\"x_refsource_MISC\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"OpenSIPS is a Session Initiation Protocol (SIP) server implementation. In versions prior to 3.6.6 and 4.0.0-rc1, the TCP message framing layer parses the Content-Length header using unsigned int arithmetic with no overflow check. When an attacker sends a Content-Length value that overflows unsigned int (e.g., 4294967296), the framing layer computes a wrapped-around value (e.g., 0) and splits the TCP stream at the wrong boundary, causing the body of the first SIP message to be processed as a separate message and enabling SIP message smuggling. Because Content-Length is parsed in the transport layer before authentication, an unauthenticated, network-based attacker can smuggle arbitrary SIP messages over any TCP-based transport (proto_tcp, proto_tls, proto_ws, proto_wss) on any instance with TCP enabled, with no routing-script preconditions. This allows smuggled messages to bypass front-end SBC/proxy security policies, inherit the connection\u0027s authentication context, and evade rate limiting. This issue has been fixed in versions 3.6.6 and 4.0.0-rc1.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-190\", \"description\": \"CWE-190: Integer Overflow or Wraparound\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2026-08-04T21:56:57.422Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2026-45103\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T17:55:45.043Z\", \"dateReserved\": \"2026-05-08T19:27:26.699Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2026-08-04T21:56:57.422Z\", \"assignerShortName\": \"GitHub_M\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
Loading…
Loading…