CVE-2026-45103

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-52979 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 4, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
Fix named in the CVE record. Sources: github, github_commit.
GitHub commit

commit 5f103eff (OpenSIPS/opensips)

Fix landed in OpenSIPS/opensips commit 5f103eff — awaiting tagged release

https://github.com/OpenSIPS/opensips/commit/5f103eff
GitHub commit

commit 4d23613b (OpenSIPS/opensips)

Fix landed in OpenSIPS/opensips commit 4d23613b — awaiting tagged release

https://github.com/OpenSIPS/opensips/commit/4d23613b
GitHub advisoryMentions a patch (unverified)

SIP Message Smuggling via TCP Content-Length Integer Overflow · Advisory · OpenSIPS/opensips · GitHub

https://github.com/OpenSIPS/opensips/security/advisories/GHSA-jv35-555v-54jh

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 138 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 38 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  4. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  5. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  6. 2026-10-25 14:27 UTCEG score recompute
  7. 2026-10-25 01:06 UTCEG score recompute
  8. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-10-18 03:38 UTCEG score recompute
  15. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-10-17 13:46 UTCEG score recompute
  17. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  21. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  22. 2026-10-12 16:04 UTCEG score recompute
  23. 2026-10-11 19:46 UTCEG score recompute
  24. 2026-10-11 17:01 UTCEG score recompute
  25. 2026-10-11 14:26 UTCEG score recompute
Show 75 more
  1. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-10-06 23:41 UTCEG score recompute
  7. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  8. 2026-10-05 19:40 UTCEG score recompute
  9. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-04 23:38 UTCEG score recompute
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-04 06:09 UTCEG score recompute
  13. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-10-03 01:54 UTCEG score recompute
  15. 2026-10-02 10:05 UTCEG score recompute
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  17. 2026-10-01 02:25 UTCEG score recompute
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-09-29 06:24 UTCEG score recompute
  20. 2026-09-27 17:59 UTCEG score recompute
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-09-25 04:40 UTCEG score recompute
  24. 2026-09-24 01:51 UTCEG score recompute
  25. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  26. 2026-09-22 15:09 UTCEG score recompute
  27. 2026-09-22 03:04 UTCEG score recompute
  28. 2026-09-20 20:51 UTCEG score recompute
  29. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  30. 2026-09-20 02:02 UTCEG score recompute
  31. 2026-09-19 03:32 UTCEG score recompute
  32. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  33. 2026-09-18 03:19 UTCEG score recompute
  34. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  35. 2026-09-17 01:10 UTCEG score recompute
  36. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  37. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  38. 2026-09-15 16:45 UTCEG score recompute
  39. 2026-09-13 23:52 UTCEG score recompute
  40. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  41. 2026-09-13 01:39 UTCEG score recompute
  42. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  43. 2026-09-11 16:19 UTCEG score recompute
  44. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  45. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  46. 2026-09-10 17:59 UTCEG score recompute
  47. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  48. 2026-09-09 08:08 UTCEG score recompute
  49. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  50. 2026-09-07 18:28 UTCEG score recompute
  51. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  52. 2026-09-06 16:47 UTCEG score recompute
  53. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  54. 2026-09-05 18:31 UTCEG score recompute
  55. 2026-09-05 04:03 UTCEG score recompute
  56. 2026-09-04 10:07 UTCEG score recompute
  57. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  58. 2026-09-03 07:18 UTCEG score recompute
  59. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  60. 2026-09-01 20:48 UTCEG score recompute
  61. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  62. 2026-08-30 21:06 UTCEG score recompute
  63. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  64. 2026-08-30 09:58 UTCEG score recompute
  65. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  66. 2026-08-29 21:41 UTCEG score recompute
  67. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  68. 2026-08-27 19:57 UTCEG score recompute
  69. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  70. 2026-08-26 19:09 UTCEG score recompute
  71. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  72. 2026-08-25 19:52 UTCEG score recompute
  73. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  74. 2026-08-24 21:39 UTCEG score recompute
  75. 2026-08-24 10:08 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-45103?
CVE-2026-45103 is a high-severity vulnerability; its CVE record was published on August 4, 2026. 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…
When was the CVE record for CVE-2026-45103 published?
The CVE record for CVE-2026-45103 was published on August 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-45103 actively exploited?
CVE-2026-45103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45103?
CVE-2026-45103 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45103?
The CVE record for CVE-2026-45103 names the fix: "This issue has been fixed in versions 3.6.6 and 4.0.0-rc1."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-45103

Explore →

Is Your Infrastructure Affected by CVE-2026-45103?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.