CVE-2026-45100: Buffer Overflow in OpenSIPS {s.b64encode} String Transformation
CVE-2026-45100 is a buffer overflow vulnerability in OpenSIPS affecting versions 3.4.0-beta through 3.6.5 and 4.0.0-beta. The flaw is in the {s.b64encode} string transformation, where the implementation checks only whether the pre-encoding input fits within a 64 KB transformation buffer. Because base64 encoding increases output size by roughly one third, inputs of approximately 49,153 to 65,535 bytes can produce encoded output that exceeds the destination buffer and overflows it by as much as 21,844 bytes. The overflow occurs in transformation buffers that are adjacent in memory and reused across chained transformations, allowing attacker-controlled data to corrupt neighboring buffer contents and values subsequently consumed while processing the same SIP message. Exploitation is remote if a deployment's routing script applies {s.b64encode} to attacker-controlled SIP message data such as a sufficiently large header value.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows remote memory corruption within OpenSIPS message-processing logic. The overflow can overwrite adjacent transformation buffers with attacker-controlled data, corrupting values used by later transformations on the same SIP message. Based on the available information, the primary demonstrated impacts are high integrity impact and high availability impact, including malformed processing state and potential service disruption or crash. The available information does not establish confidentiality impact.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by preventing routing logic from applying {s.b64encode} to attacker-controlled SIP fields, especially large header values. Review routing scripts for any transformation chains that process untrusted input with {s.b64encode}, and enforce strict size limits on SIP headers or other user-controlled values before transformation. Additional defensive measures include rejecting unusually large SIP messages or headers at the edge to prevent the oversized input required to trigger the overflow.
Remediation
Patch, then assume compromise.
Upgrade OpenSIPS to a fixed release. The issue is fixed in version 3.6.6 and in 4.0.0-rc1. Affected deployments running versions 3.4.0-beta through 3.6.5 or 4.0.0-beta should move to a patched version as soon as operationally feasible.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-45100 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-45100 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-45100?
- Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-45100.
- Is there a patch for CVE-2026-45100?
- Upgrade OpenSIPS to a fixed release. The issue is fixed in version 3.6.6 and in 4.0.0-rc1.
- How severe is CVE-2026-45100?
- CVE-2026-45100 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 0.83% (58th percentile) as of Sep 25, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.