# CVE-2026-73215: The coturn server can end in a state where it does not accept more requests with "even-port" enabled.

> An authenticated attacker can exhaust the relay port pool in coturn when even-port mode is enabled, causing subsequent allocation failures and denial of service.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-73215, GHSA-847g-qmc6-6m4r, MINI-gqrm-9h5x-q328, UBUNTU-CVE-2026-73215

## What is CVE-2026-73215?

CVE-2026-73215 is a high-severity denial of service vulnerability in coturn, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Coturn is a free open source implementation of TURN and STUN Server. Prior to 4.17.0, turnports_allocate_even() in src/apps/relay/turn_ports.c marks the unused odd sibling port as TPS_TAKEN_ODD for an EVEN-PORT Allocate request with reservation bit R=0 even though no RTCP socket will release it, allowing an authenticated client to permanently exhaust the relay port pool and cause subsequent allocations to fail with STUN error 508. This issue is fixed in version 4.17.0.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-73215?


## How do I fix CVE-2026-73215?

Upgrade to a fixed version.

## Is CVE-2026-73215 being exploited?

There is no known exploitation of CVE-2026-73215 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73215 and fix it if it is affected.

What it is: CVE-2026-73215 is a high-severity denial of service vulnerability in coturn, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73215 in the wild and no public exploit code.

Affected product: coturn. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73215/ (Markdown: https://insights.sbomify.com/CVE-2026-73215/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73215
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73215
- OSV: https://osv.dev/vulnerability/CVE-2026-73215

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73215/
Summaries are generated and may contain mistakes; the official description above is the record.