{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65981 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-65981 is a high-severity authentication bypass vulnerability in coturn, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-65981 and fix it if it is affected.\n\nWhat it is: CVE-2026-65981 is a high-severity authentication bypass vulnerability in coturn, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65981 exists.\n\nAffected product: coturn. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-65981/ (Markdown: https://insights.sbomify.com/CVE-2026-65981/index.md)","id":"CVE-2026-65981","markdown":"https://insights.sbomify.com/CVE-2026-65981/index.md","name":"CVE-2026-65981","record":{"aliases":["DEBIAN-CVE-2026-65981","GHSA-69wx-x7x6-pjj8","UBUNTU-CVE-2026-65981"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"TURN/STUN server","requires_auth":"low_privilege","summary":"An authenticated attacker can hijack another user's TURN allocation by exploiting a missing identity check during session resumption with mobility tickets.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Coturn: MOBILITY-TICKET session-resume authorization bypass allows cross-user TURN allocation takeover","id":"CVE-2026-65981","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"FUXA: JWT lifecycle flaws allow deleted or demoted users to retain privileged sessions","id":"CVE-2026-65984"},"packages":[],"prev":{"headline":"Chartbrew: SQL Injection via Missing Backslash Escaping in ClickHouse Variable Substitution","id":"CVE-2026-65980"},"products":["coturn"],"published":"2026-07-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-05","vendors":["coturn"]},"summary":"An authenticated attacker can hijack another user's TURN allocation by exploiting a missing identity check during session resumption with mobility tickets.","url":"https://insights.sbomify.com/CVE-2026-65981/"}