{"id":"CVE-2026-65981","aliases":["DEBIAN-CVE-2026-65981","EUVD-2026-51651","GHSA-69wx-x7x6-pjj8","UBUNTU-CVE-2026-65981","openSUSE-SU-2026:11617-1"],"status":"published","title":"Coturn: MOBILITY-TICKET session-resume authorization bypass allows cross-user TURN allocation takeover","description":"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.","severity":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00389,"percentile":0.33427,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-639"],"published":"2026-07-31T21:00:02Z","modified":"2026-10-28T10:58:02Z","fixes":[{"ecosystem":"Debian:14","package":"coturn","fixed_in":["4.15.0-1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.12.0-1","4.14.0-1","4.15.0-1","4.18.0-1","4.6.1-1","4.6.1-2"]},{"source":"osv","ecosystem":"Debian:13","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.12.0-1","4.14.0-1","4.15.0-1","4.18.0-1","4.6.1-2"]},{"source":"osv","ecosystem":"Debian:14","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1"}]}],"versions":["4.12.0-1","4.14.0-1","4.6.1-2"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.5.4-2","4.5.0.2-3","4.5.0.3-1","4.5.0.3-1build1","4.5.0.3-1ubuntu0.2","4.5.0.3-1ubuntu0.3","4.5.0.3-1ubuntu0.4"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.5.0.6-1ubuntu2","4.5.0.7-1ubuntu1","4.5.0.7-1ubuntu2","4.5.0.7-1ubuntu2.18.04.1","4.5.0.7-1ubuntu2.18.04.2","4.5.0.7-1ubuntu2.18.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.5.1.1-1.1build1","4.5.1.1-1.1build2","4.5.1.1-1.1ubuntu0.20.04.1","4.5.1.1-1.1ubuntu0.20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.5.2-3","4.5.2-3.1~ubuntu22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.6.1-1build1","4.6.1-1build2","4.6.1-1build3","4.6.1-1build4"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.6.1-2build2","4.12.0-1","4.14.0-1","4.15.0-1","4.18.0-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.6.1-2build1","4.6.1-2build2"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"coturn","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.17.2-1.1"}]}],"bundled":17}],"products":[{"vendor":"coturn","product":"coturn"}],"references":[{"url":"https://github.com/coturn/coturn/security/advisories/GHSA-69wx-x7x6-pjj8","tags":["x_refsource_CONFIRM","exploit","advisory","report"]},{"url":"https://github.com/coturn/coturn/commit/37df0513168f830a7c9ce0a411db0300fa182f05","tags":["x_refsource_MISC","fix","report"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/65xxx/CVE-2026-65981.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-65981","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-65981","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-65981","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-65981","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2026-40613","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-62959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-65981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68553","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68554","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73216","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2026-65981","title":"Coturn: MOBILITY-TICKET session-resume authorization bypass allows cross-user TURN allocation takeover","description":"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.","status":"published","published":"2026-07-31T21:00:02.893Z","modified":"2026-08-05T13:44:34.433Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","level":"high","assessor":"cna"}],"cwes":["CWE-639"],"updated_at":"2026-11-02T13:37:02.780526Z"}],"euvd":[{"id":"EUVD-2026-51651","description":"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.","status":"published","published":"2026-07-31T21:00:02Z","modified":"2026-08-05T13:44:34Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","level":"high"}],"updated_at":"2026-11-02T18:02:10.319044Z"}],"nvd":[{"id":"CVE-2026-65981","description":"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.","status":"published","published":"2026-07-31T21:17:31.857Z","modified":"2026-09-09T20:55:04.493Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","level":"high","assessor":"secondary"}],"cwes":["CWE-639"],"updated_at":"2026-11-02T14:12:34.290716Z"}],"osv":[{"id":"CVE-2026-65981","title":"Coturn: MOBILITY-TICKET session-resume authorization bypass allows cross-user TURN allocation takeover","description":"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.","status":"published","published":"2026-07-31T21:00:02.893Z","modified":"2026-10-28T10:58:02.540973833Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","level":"high"}],"cwes":["CWE-639"],"updated_at":"2026-11-02T15:45:14.46177Z"},{"id":"DEBIAN-CVE-2026-65981","description":"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.","status":"published","published":"2026-07-31T21:17:31.857Z","modified":"2026-10-10T16:00:07.48405588Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","level":"high"}],"updated_at":"2026-11-02T15:45:58.699079Z"},{"id":"UBUNTU-CVE-2026-65981","description":"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.","status":"published","published":"2026-07-31T21:17:00Z","modified":"2026-10-17T12:59:17.406549982Z","cvss":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","level":"high"}],"updated_at":"2026-11-02T16:56:53.710209Z"},{"id":"openSUSE-SU-2026:11617-1","title":"coturn-4.17.2-1.1 on GA media","description":"These are all security issues fixed in the coturn-4.17.2-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-08-27T00:00:00Z","modified":"2026-08-28T18:23:08.654818419Z","updated_at":"2026-11-02T16:58:39.516824Z"}]}}