RESIPROCATE · CVE-2026-122126 · Package
NO FIX YET · SEE WHAT TO DO
The reTurn TURN client in reSIProcate through 1.14.0 has a heap buffer overflow in TurnTcpSocket::handleReadHeader() where frame lengths are not checked against the 8192-byte read buffer. A malicious TURN server can send frames declaring up to 65535 bytes, overwriting roughly 57 KB of adjacent memory and crashing the client.
first public Nov 4, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Applications that use the synchronous reTurn TURN client (TurnTcpSocket, and TurnTlsSocket which inherits it) from reSIProcate 1.14.0 or earlier, typically VoIP or WebRTC clients. A malicious TURN server, or anyone who can write into a plain TCP stream to the client, can send an oversized frame and overwrite up to about 57 KB of heap, which crashes the client. Applications that do not use the reTurn client, or that only talk to trusted TURN servers, can mostly skip it.
Not affected if no-return-client-use, trusted-turn-servers-only
Who cares resiprocate, turn-client, voip, webrtc
reSIProcate reTurn client through 1.14.0 contains a heap buffer overflow in TurnTcpSocket::handleReadHeader() that allows malicious TURN servers 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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
1.14.0 is the latest and is affected)NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.