Skip to content
VulniPulse
Critical9.9Red Hat Linux

Critical [CVE-2026-73213] Server-Side Request Forgery via incorrect IPv6 comparison

This critical-severity Red Hat Linux advisory covers CVE-2026-73213.

CVE-2026-73213 Published Aug 11, 2026Updated by vendor Aug 11, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Coturn is a free open source implementation of TURN and STUN Server.

Prior to 4.16.0, addr_less_eq() in src/client/ns_turn_ioaddr.c uses a component-wise comparison for native IPv6 min-max intervals in ioa_addr_in_range(), allowing an authenticated TURN client to relay to an IPv6 peer that is numerically within a configured non-prefix-aligned denied-peer-ip range but is classified as outside it.

This issue is fixed in version 4.16.0. A flaw was found in Coturn.

An authenticated TURN client can bypass configured IP address restrictions due to an incorrect component-wise IPv6 comparison in the `addr_less_eq()` function. This allows the client to relay traffic to an IPv6 peer that should be denied, leading to a Server-Side Request Forgery (SSRF) vulnerability.

Red Hat products do not ship Coturn. The community packages (Fedora, EPEL) ship Coturn 4.16.0 which includes the fix for this vulnerability.

Red Hat severity: Critical — CVSS 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). Weakness: CWE-918.

Affected versions
  • < 4.16.0

Official advisory · high-confidence parse· fetched 3 hours ago·verify at source

Fixed versions
  • 4.16.0

Official advisory · high-confidence parse· fetched 3 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Update Coturn to version 4.16.0 or later, which replaces the incorrect component-wise IPv6 comparison with a correct memcmp-based ordering.

Official advisory · high-confidence parse· fetched 3 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.