CVE-2026-65981

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.1(medium)
EG Risk
48(Track*)
EG Risk 48/100SSVC: Track*

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
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

July 31, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jul 31, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

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 rangeFixed inDependents
coturn4.12.0-1 ... 4.6.1-2 (7 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
coturn4.12.0-1, 4.14.0-1, 4.15.0-1, 4.6.1-1, 4.6.1-2——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
coturn4.12.0-1, 4.14.0-1, 4.15.0-1, 4.6.1-2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
coturn4.12.0-1, 4.14.0-1, 4.6.1-24.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 / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-27 20:46 UTCEG score recompute
  2. 2026-08-26 14:49 UTCEG score recompute
  3. 2026-08-26 14:47 UTCEPSS rescore
  4. 2026-08-26 02:16 UTCEG score recompute
  5. 2026-08-25 13:49 UTCEPSS rescore
  6. 2026-08-25 01:08 UTCEG score recompute
  7. 2026-08-24 12:35 UTCEG score recompute
  8. 2026-08-23 11:27 UTCEG score recompute
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 10:19 UTCEG score recompute
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 09:12 UTCEG score recompute
  13. 2026-08-20 22:56 UTCEPSS rescore
  14. 2026-08-19 19:30 UTCEG score recompute
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 18:22 UTCEG score recompute
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 16:33 UTCEG score recompute
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-16 15:12 UTCEG score recompute
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:38 UTCEG score recompute
  23. 2026-08-15 01:31 UTCEG score recompute
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 00:25 UTCEG score recompute
Show 32 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-12 23:18 UTCEG score recompute
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-11 22:11 UTCEG score recompute
  5. 2026-08-11 09:36 UTCEG score recompute
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-09 19:57 UTCEG score recompute
  8. 2026-08-09 13:47 UTCEPSS rescore
  9. 2026-08-08 18:51 UTCEG score recompute
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-07 17:44 UTCEG score recompute
  12. 2026-08-06 16:38 UTCEG score recompute
  13. 2026-08-06 13:47 UTCEPSS rescore
  14. 2026-08-06 04:04 UTCEG score recompute
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-05 15:31 UTCEG score recompute
  18. 2026-08-05 14:38 UTCEG score recompute
  19. 2026-08-04 18:04 UTCEG score recompute
  20. 2026-08-04 15:10 UTCEPSS rescore
  21. 2026-08-04 10:39 UTCEPSS rescore
  22. 2026-08-04 05:28 UTCEG score recompute
  23. 2026-08-04 04:39 UTCEG score recompute
  24. 2026-08-03 18:18 UTCEG score recompute
  25. 2026-08-03 18:00 UTCEG score recompute
  26. 2026-08-03 12:08 UTCEG score recompute
  27. 2026-08-03 10:36 UTCEPSS rescore
  28. 2026-08-02 11:01 UTCEG score recompute
  29. 2026-08-02 02:27 UTCEPSS rescore
  30. 2026-07-31 21:21 UTCEG score recompute
  31. 2026-07-31 21:09 UTCEG score recompute
  32. 2026-07-31 21:08 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-65981?
CVE-2026-65981 is a high vulnerability 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 CVE-2026-65981 disclosed?
CVE-2026-65981 was first published in the National Vulnerability Database on July 31, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65981 actively exploited?
CVE-2026-65981 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.9% of all scored CVEs.
What is the CVSS score of CVE-2026-65981?
CVE-2026-65981 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-65981?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65981, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs