CVE-2026-45100: OpenSIPS: Buffer Overflow in Base64 Encode Transformation
OpenSIPS is a Session Initiation Protocol (SIP) server implementation. Versions 3.4.0-beta through 3.6.5 and 4.0.0-beta contain a buffer overflow in the {s.b64encode} string transformation. The size check for {s.b64encode} only verifies that the input fits within the 64 KB transformation buffer, but base64 encoding expands the data by roughly a third, so an input between about 49,153 and 65,535 bytes produces more output than the buffer can hold and overflows it by up to 21,844 bytes. Because these transformation buffers sit next to each other in memory and are reused for chained transformations, the overflow writes attacker-controlled data into the adjacent buffer and corrupts values used by later transformations processing the same SIP message. A remote attacker can trigger this by sending a SIP message with a large header value (roughly 50,000 bytes or more) when the routing script applies {s.b64encode} to attacker-controlled input, making exploitability dependent on the deployment's routing configuration. This issue has been fixed in versions 3.6.6 and 4.0.0-rc1.
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated sender may corrupt OpenSIPS memory when a vulnerable routing script Base64-encodes a very large attacker-controlled SIP value. Successful triggering could disrupt service or alter subsequent message processing. Exposure depends on configuration; merely running an affected version does not prove exploitability.
Executive priority
Prioritize immediate assessment of externally reachable SIP infrastructure. Expedite upgrades wherever affected versions combine with attacker-controlled {s.b64encode} processing. Treat confirmed vulnerable paths as urgent because exploitation requires no authentication and may compromise service integrity or availability, while avoiding claims of active exploitation unsupported by current evidence.
Technical view
In affected OpenSIPS versions, {s.b64encode} checks input size against a 64 KB buffer without accounting for Base64 expansion. Inputs around 49,153–65,535 bytes can overflow into an adjacent reusable transformation buffer by up to 21,844 bytes, corrupting values consumed by later transformations. CVSS 3.1 is 9.1, affecting integrity and availability.
Likely exposure
Highest where network-reachable SIP services run affected versions and routing scripts apply {s.b64encode} to attacker-controlled headers or other message values. Deployments not using this transformation on untrusted input may not expose the vulnerable path, but version and routing configuration must both be checked.
Exploitation context
The supplied sources describe remote, low-complexity triggering without privileges or user interaction. Exploitability requires a suitable routing configuration and a large attacker-controlled SIP value. KEV is false, and the supplied evidence does not establish active exploitation or reliable code execution in the wild.
Researcher notes
The overwrite targets an adjacent transformation buffer reused during chained processing, making later transformations within the same SIP message relevant to impact. The source establishes attacker-controlled corruption but does not establish confidentiality loss or arbitrary code execution. Configuration review is essential for distinguishing installed-version exposure from a reachable vulnerable data flow.
Mitigation direction
Upgrade affected 3.x deployments to OpenSIPS 3.6.6 or later.
Upgrade affected 4.x deployments to OpenSIPS 4.0.0-rc1 or later.
Until upgraded, avoid applying {s.b64encode} to attacker-controlled SIP values.
Restrict untrusted SIP reachability where operationally feasible.
Check OpenSIPS vendor guidance for any additional deployment-specific precautions.
Validation and detection
Inventory OpenSIPS versions and identify instances within the affected ranges.
Search routing scripts for every use of {s.b64encode}.
Trace whether untrusted headers or message values can reach those transformations.
Confirm upgraded instances report version 3.6.6, 4.0.0-rc1, or later.
Verify ingress controls reject unexpectedly large SIP values before vulnerable processing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-120 · source CWE mapping
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.