Description
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.
Published: 2026-08-04
Score: 9.1 Critical
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

OpenSIPS employs a string transformation, {s.b64encode}, that expands data by roughly a third. The transformation buffer limit of 64 KB is not compensated for this expansion, so an input of about 49 kB to 65 kB can overflow the buffer by up to 21 kB. The overflow writes attacker‑controlled data into an adjacent buffer used by later transformations, potentially corrupting control data and leading to remote code execution or arbitrary memory corruption. This is a classic stack-based buffer overflow (CWE‑120).

Affected Systems

Versions 3.4.0‑beta through 3.6.5 and 4.0.0‑beta of OpenSIPS are vulnerable. The issue was fixed in 3.6.6 and 4.0.0‑rc1. All other versions not listed are assumed unaffected unless proven otherwise.

Risk and Exploitability

The CVSS score is 9.1, indicating high severity. No EPSS score is available and the vulnerability is not listed in CISA KEV. Exploitation requires a SIP message with a header value of roughly 50 kB or more when the routing script applies {s.b64encode} to attacker controlled input, making the attack highly dependent on deployment configuration. If the configuration applies the transformation, an off‑the‑shelf exploit can trigger the overflow and, if successful, could lead to arbitrary code execution or denial of service.

Generated by OpenCVE AI on August 4, 2026 at 23:19 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade OpenSIPS to version 3.6.6 or newer (or 4.0.0‑rc1 or newer) which removes the vulnerability.
  • Review and adjust routing scripts to ensure that {s.b64encode} is not applied to untrusted or user‑controlled SIP header values. If necessary, eliminate the transformation from the routing flow.
  • Enforce input validation or size limits on SIP header values before they reach the transformation to prevent oversized inputs from triggering the buffer overflow.

Generated by OpenCVE AI on August 4, 2026 at 23:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 04 Aug 2026 23:45:00 +0000

Type Values Removed Values Added
First Time appeared Opensips
Opensips opensips
Vendors & Products Opensips
Opensips opensips

Tue, 04 Aug 2026 22:15:00 +0000

Type Values Removed Values Added
Description 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.
Title OpenSIPS: Buffer Overflow in Base64 Encode Transformation
Weaknesses CWE-120
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}


Subscriptions

Opensips Opensips
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-04T21:44:40.109Z

Reserved: 2026-05-08T19:27:26.698Z

Link: CVE-2026-45100

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T23:30:15Z

Weaknesses
  • CWE-120

    Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')