Coturn is a free open source implementation of TURN and STUN Server. From 4.5.2 through 4.14.0, when Coturn is started with --acme-redirect and exposes a plaintext-TCP listener, an unauthenticated remote client can send a single ordinary HTTP GET request and receive a 301 response whose Location header contains up to ~870 bytes of adjacent process heap memory. The leaked region is a recycled network receive buffer that is reused without being zeroed, so on a busy server it can contain data from other clients' requests (TURN credentials, OAuth tokens, relayed payloads). Root cause is a signed→unsigned conversion. This issue is fixed in version 4.15.0.
CVE-2026-62959
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EG Risk
- 68(Attend)EG Risk 68/100SSVC: Attend
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 computedSeverity82% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
July 31, 2026
Last Modified
August 1, 2026
Advisory Details (4)
Auto-updated Jul 31, 2026Pre-authentication heap memory disclosure in coturn ACME redirect (`try_acme_redirect`) · Advisory · coturn/coturn · GitHub
https://github.com/coturn/coturn/security/advisories/GHSA-m23x-5qf5-988g4.15.0
Patch available: coturn/coturn 4.15.0
https://github.com/coturn/coturn/releases/tag/4.15.0fix: reject ACME requests via signed return
Patch available: coturn/coturn 4.15.0 (PR #1965 merged 2026-06-28)
https://github.com/coturn/coturn/pull/1965commit 960835886692 (coturn/coturn)
Patch available: coturn/coturn 4.15.0 (contains commit 960835886692)
https://github.com/coturn/coturn/commit/960835886692fa04cf63ddd970c3f330740c87f4Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| coturn | 4.12.0-1 ... 4.6.1-2 (7 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| coturn | 4.12.0-1, 4.14.0-1, 4.15.0-1, 4.6.1-1, 4.6.1-2 | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| coturn | 4.12.0-1, 4.14.0-1, 4.15.0-1, 4.6.1-2 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| coturn | 4.12.0-1, 4.14.0-1, 4.6.1-2 | 4.15.0-1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 49× 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.
- 2026-08-25 17:48 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 17:46 UTCEG score recompute
- 2026-08-23 04:15 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 04:13 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 04:04 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 03:59 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 15:50 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:39 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 02:38 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:36 UTCEG score recompute
- 2026-08-15 02:33 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 02:30 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 14:27 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 14:25 UTCEG score recompute
Show 24 moreShow fewer
- 2026-08-11 02:23 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 14:19 UTCEG score recompute
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 02:19 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 02:16 UTCEG score recompute
- 2026-08-06 14:13 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 02:11 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 00:54 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 12:53 UTCEG score recompute
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 12:50 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 12:36 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 00:32 UTCEG score recompute
- 2026-07-31 23:40 UTCEG score recompute
- 2026-07-31 20:21 UTCEG score recompute
- 2026-07-31 20:18 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-62959?
When was CVE-2026-62959 disclosed?
Is CVE-2026-62959 actively exploited?
What is the CVSS score of CVE-2026-62959?
How do I remediate CVE-2026-62959?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62959
Is Your Infrastructure Affected by CVE-2026-62959?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.