CVE-2026-122126 — CWE-122
CVE-2026-122126 is a MEDIUM severity Memory Corruption / Buffer Overflow vulnerability (CWE-122) (CVSS 5.9/10) affecting affected software system. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) with zero user interaction (UI:N), allowing unauthorized disclosure of sensitive data (C:H).
📄 Official NVD / MITRE Original Record Text
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-122126
CVSS 5.9/10 · MEDIUM · 04.11.2026
CWE: CWE-122
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Buffer Overflow / Memory Corruption
Summary: 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 …
⚡ ATTACK CHAIN
1. Fuzz with Boofuzz/AFL++ to find crash.
2. Find offset: pattern_create→crash→pattern_offset EIP
3. Control EIP/RIP, bypass NX with ROP chains.
4. ASLR bypass via info leak or brute force.
5. Metasploit: search CVE-XXXX; use exploit/...; run
🔧 Tools: GDB+PEDA/pwndbg, ROPgadget, pwntools, Metasploit, AFL++
🗺️ MITRE ATT&CK: T1203 (Exploitation for Client Execution), T1068
🌍 REAL WORLD IMPACT
All confidential data readable/stealable; service can be completely taken down.
🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Verify ASLR/NX/Stack Canary are active.
→ Pre-patch: put service behind VPN or apply IP allowlist.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
📋 Routine update cycle (30 days)
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]