CVE-2026-65981: Coturn: MOBILITY-TICKET session-resume authorization bypass allows cross-user TURN allocation takeover
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 handleturnrefresh resume branch, the victim allocation (origss) is located solely by the attacker-controlled mobile id, and credentials are only adopted (via copyauthparameters) when the resuming session is unauthenticated. Because the attacker's session already has hmackeyset set to 1 from its own prior authentication (which is never reset for long-term-credential sessions), the credential copy is skipped and checkstunauth validates the REFRESH against the attacker's own identity rather than the allocation owner's. This issue is fixed in version 4.15.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
coturnto a version that resolves this vulnerability.Fixed in 4.15.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-65981?
The severity of CVE-2026-65981 is classified as high with a score of 7.1.
How do I fix CVE-2026-65981?
To fix CVE-2026-65981, upgrade your Coturn server to version 4.15.0 or later.
What can an attacker do with CVE-2026-65981?
An attacker can exploit CVE-2026-65981 to gain unauthorized access to TURN allocations, allowing cross-user TURN allocation takeover.
Which versions of Coturn are affected by CVE-2026-65981?
CVE-2026-65981 affects Coturn versions prior to 4.15.0.
What is the cause of CVE-2026-65981?
CVE-2026-65981 is caused by the failure to verify that the resuming user's credentials match the original allocation owner.