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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
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.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- resiprocate resiprocate
through 1.14.0
Evidence 5
- Patch
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122126
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: cve.now feed data
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: vulncheck.com
Which versions are affected by CVE-2026-122126?
resiprocate: through 1.14.0.Source: cve.now feed data
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: vulncheck.com
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: vulncheck.com