Buffer Overflow Affecting coturn package, versions <4.12.0-1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.68% (50th 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-DEBIANUNSTABLE-COTURN-17379698
  • published19 Jun 2026
  • disclosed18 Jun 2026

Introduced: 18 Jun 2026

CVE-2026-43994  (opens in a new tab)
CWE-120  (opens in a new tab)

How to fix?

Upgrade Debian:unstable coturn to version 4.12.0-1 or higher.

NVD Description

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

Coturn is a free open source implementation of TURN and STUN Server. Versions prior to 4.10.0 contain a stack buffer overflow in decode_oauth_token_gcm(). A uint16_t nonce_len field read from an attacker-supplied OAuth access token (0-65535) is passed directly to memcpy() as the copy length into a 256-byte stack buffer (oauth_encrypted_block.nonce[256]) without bounds checking. The overflow occurs before AES-GCM authentication is verified, the attacker does not need to know the OAuth key or produce a valid AES-GCM token. Up to 735 bytes of attacker-controlled data are written past the buffer, may corrupt adjacent stack data, including control-flow data depending on compiler, ABI, and mitigations. Requires --oauth mode (non-default). This may provide a plausible RCE primitive depending on exploit mitigations; because coturn is widely deployed for WebRTC TURN/STUN and --oauth is commonly recommended, impact can be broad. This issue has been fixed in version 4.10.0.