Buffer overflow in Resiprocate
CVE-2026-122126
reSIProcate reTurn client through 1.14.0 contains a heap buffer overflow in TurnTcpSocket::handleReadHeader(), which TurnTlsSocket inherits, that allows malicious TURN servers or on-path attackers to overwrite memory via oversized frame lengths. Attackers can send STUN or ChannelData frames declaring up to 65535 bytes, writing roughly 57 KB past the fixed 8192-byte mReadBuffer and crashing the client. Only the synchronous TCP and TLS client is affected; the asynchronous client (TurnAsyncSocket) and the reTurn server are not.
Vulnerability class: Buffer Overflow
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
Weakness classification (CWE)
References
- github.com/resiprocate/resiprocate (product)
- github.com/resiprocate/resiprocate/blob/resiprocate-1.14.0/reTurn/client/TurnTc… (technical-description)
- Patch Commit (patch)
- Pull Request #496 (issue-tracking, patch)
- VulnCheck Advisory: reSIProcate reTurn client through 1.14.0 Heap Buffer Overflow via TurnTcpSocket (third-party-advisory)
Frequently asked questions
- What is CVE-2026-122126?
- CVE-2026-122126 is a medium-severity vulnerability in Resiprocate, classified under Heap-based Buffer Overflow. CVSS score: 5.9/10. Published 2026-11-04.
- How severe is CVE-2026-122126?
- Medium severity. CVSS v3 base score is 5.9 out of 10.