CVE-2026-65981

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 31, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Jul 31, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

MOBILITY-TICKET session-resume authorization bypass allows cross-user TURN allocation takeover · Advisory · coturn/coturn · GitHub

https://github.com/coturn/coturn/security/advisories/GHSA-69wx-x7x6-pjj8
GitHub commit Patch Available

commit 37df0513168f (coturn/coturn)

Patch available: coturn/coturn 4.15.0 (contains commit 37df0513168f)

https://github.com/coturn/coturn/commit/37df0513168f830a7c9ce0a411db0300fa182f05

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.12.0-1 ... 4.6.1-2 (7 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.12.0-1 ... 4.6.1-2 (6 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.12.0-1, 4.14.0-1, 4.15.0-1, 4.18.0-1, 4.6.1-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
coturn4.12.0-1, 4.14.0-1, 4.6.1-2
  • every version up to 4.15.0-1: fixed in 4.15.0-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 125 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 25 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-12 15:46 UTCEG score recompute
  3. 2026-10-11 19:31 UTCEG score recompute
  4. 2026-10-11 16:46 UTCEG score recompute
  5. 2026-10-11 14:07 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-06 23:50 UTCEG score recompute
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-05 19:54 UTCEG score recompute
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-04 23:50 UTCEG score recompute
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-04 06:28 UTCEG score recompute
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-02 16:48 UTCEG score recompute
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-10-01 02:46 UTCEG score recompute
  23. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-09-29 06:49 UTCEG score recompute
  25. 2026-09-27 18:38 UTCEG score recompute
Show 75 more
  1. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-09-25 04:51 UTCEG score recompute
  3. 2026-09-23 23:50 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  5. 2026-09-22 21:34 UTCEG score recompute
  6. 2026-09-22 07:35 UTCEG score recompute
  7. 2026-09-20 21:13 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-09-19 23:41 UTCEG score recompute
  10. 2026-09-19 03:58 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-09-18 01:15 UTCEG score recompute
  13. 2026-09-17 01:23 UTCEG score recompute
  14. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-09-16 05:27 UTCEG score recompute
  16. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-09-13 17:10 UTCEG score recompute
  18. 2026-09-12 16:03 UTCEG score recompute
  19. 2026-09-11 14:56 UTCEG score recompute
  20. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-09-10 12:55 UTCEG score recompute
  23. 2026-09-09 07:01 UTCEG score recompute
  24. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  25. 2026-09-07 19:25 UTCEG score recompute
  26. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  27. 2026-09-06 20:46 UTCEG score recompute
  28. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  29. 2026-09-05 18:45 UTCEG score recompute
  30. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  31. 2026-09-04 16:18 UTCEG score recompute
  32. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  33. 2026-09-03 09:07 UTCEG score recompute
  34. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  35. 2026-09-01 22:30 UTCEG score recompute
  36. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  37. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  38. 2026-08-30 23:26 UTCEG score recompute
  39. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  40. 2026-08-30 10:53 UTCEG score recompute
  41. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  42. 2026-08-29 22:18 UTCEG score recompute
  43. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  44. 2026-08-27 20:46 UTCEG score recompute
  45. 2026-08-26 14:49 UTCEG score recompute
  46. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  47. 2026-08-26 02:16 UTCEG score recompute
  48. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  49. 2026-08-25 01:08 UTCEG score recompute
  50. 2026-08-24 12:35 UTCEG score recompute
  51. 2026-08-23 11:27 UTCEG score recompute
  52. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  53. 2026-08-22 10:19 UTCEG score recompute
  54. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  55. 2026-08-21 09:12 UTCEG score recompute
  56. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  57. 2026-08-19 19:30 UTCEG score recompute
  58. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  59. 2026-08-18 18:22 UTCEG score recompute
  60. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  61. 2026-08-17 16:33 UTCEG score recompute
  62. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  63. 2026-08-16 15:12 UTCEG score recompute
  64. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  65. 2026-08-16 02:38 UTCEG score recompute
  66. 2026-08-15 01:31 UTCEG score recompute
  67. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  68. 2026-08-14 00:25 UTCEG score recompute
  69. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  70. 2026-08-12 23:18 UTCEG score recompute
  71. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  72. 2026-08-11 22:11 UTCEG score recompute
  73. 2026-08-11 09:36 UTCEG score recompute
  74. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  75. 2026-08-09 19:57 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-65981?
CVE-2026-65981 is a high-severity vulnerability; its CVE record was published on July 31, 2026. 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…
When was the CVE record for CVE-2026-65981 published?
The CVE record for CVE-2026-65981 was published on July 31, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-65981 actively exploited?
CVE-2026-65981 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65981?
CVE-2026-65981 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-65981?
A fix for CVE-2026-65981 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-65981

Explore →

Is Your Infrastructure Affected by CVE-2026-65981?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs