High [CVE-2026-65981] Authorization bypass allows session takeover via MOBILITY-TICKET session resume
This high-severity Red Hat Linux advisory covers CVE-2026-65981.
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.
Summary
Coturn is a free open source implementation of TURN and STUN Server.
Prior to 4.15.0, a server using --mobility authenticates a resumed REFRESH request with the resuming user's credentials but does not verify that identity against the original allocation owner, allowing an authenticated attacker who obtains a victim MOBILITY-TICKET to receive and inject relayed traffic and consume the victim's quota.
In the handle_turn_refresh resume branch, the victim allocation (orig_ss) is located solely by the attacker-controlled mobile id, and credentials are only adopted (via copy_auth_parameters) when the resuming session is unauthenticated.
Because the attacker's session already has hmackey_set set to 1 from its own prior authentication (which is never reset for long-term-credential sessions), the credential copy is skipped and check_stun_auth validates the REFRESH against the attacker's own identity rather than the allocation owner's. This issue is fixed in version 4.15.0.
This allows the attacker to take over the victim's TURN (Traversal Using Relays around NAT) allocation. This flaw affects the community-maintained coturn TURN/STUN server as shipped in Fedora and EPEL.
Red Hat does not ship coturn in any core Red Hat product. Fedora and EPEL currently ship coturn 4.16.0, which already includes the fix released in 4.15.0, so the shipped builds are not vulnerable.
- < 4.15.0
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Mitigation checklist
- No action needed - the shipped coturn build (4.16.0) already contains the upstream fix.
Official advisory · high-confidence parse· fetched 2 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.