CVE-2026-62959
Heap memory leak in Coturn via --acme-redirect exposes sensitive data in HTTP 301 Location header.
Is CVE-2026-62959 being exploited?
Not confirmed. CVE-2026-62959 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-62959?
CVE-2026-62959 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62959?
Yes. A fix has been recorded for CVE-2026-62959. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62959 affect?
CVE-2026-62959 affects Coturn 4.5.2 - 4.14.0, STUN/TURN deployments using --acme-redirect with plaintext-TCP listeners. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62959?
Upgrade to Coturn 4.15.0; or disable --acme-redirect and plaintext-TCP listeners until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote attacker can retrieve ~870 bytes of heap memory via HTTP GET, leaking TURN creds, OAuth tokens, or relayed payloads.
Immediate action required
- affected>= 4.5.2 and < 4.15.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.