Quick answers
- Is CVE-2026-53450 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53450 being exploited in the wild.
- How severe is CVE-2026-53450?
- High severity, with a CVSS score of 7.4, published 10 July 2026.
- Which products and versions are affected?
- Coturn < 4.13.0.
- Is there a fix for CVE-2026-53450?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-53450 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-53450?
- Check whether you run Coturn at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in Coturn due to an incorrect logic sequence in the `ioa_addr_is_loopback` function. The function checks for the literal IPv6 loopback address (::1) by inspecting the final byte of the address before handling IPv4-mapped IPv6 addresses. Because the IPv4-mapped address for localhost (::ffff:127.0.0.1) also ends in a 1, the function incorrectly identifies it as a non-loopback address and returns false. An authenticated TURN client can exploit this by using the `XOR-PEER-ADDRESS` attribute to request permissions or channel bindings for the host's loopback interface. This bypasses the default `allow-loopback-peers=false` configuration, though it does not affect systems with explicit denied-peer ranges. The issue is resolved in version 4.13.0.
Affected products
- coturn coturn < 4.13.0
Timeline
- 2026-06-26: advisory: GitHub Security Advisory published
- 2026-07-10: disclosed: NVD publication date