Out-of-bounds Read Affecting coturn package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.38% (32nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-COTURN-18496013
  • published1 Aug 2026
  • disclosed31 Jul 2026

Introduced: 31 Jul 2026

NewCVE-2026-62959  (opens in a new tab)
CWE-125  (opens in a new tab)
CWE-195  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest coturn.

NVD Description

Note: Versions mentioned in the description apply only to the upstream coturn package and not the coturn package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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 <URL> 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.