# CVE-2026-118689: OvenMediaEngine through 0.21.0 OVT Relay DoS via Oversized payload_length


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-c237-3r77-c8g5

## What is CVE-2026-118689?

CVE-2026-118689 is a high-severity vulnerability in OvenMediaLabs OvenMediaEngine, published on 28 Oct 2026. 

### Official description

OvenMediaEngine through 0.21.0 contains a denial of service vulnerability in OvtPacket::LoadHeader() that allows unauthenticated attackers to stall connections by sending payload_length values above 32750. Attackers can send crafted OVT packets to the OVT listener to hold connections open indefinitely and accumulate buffered memory, disrupting origin-to-edge stream relay.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

No fix has been published for CVE-2026-118689 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118689 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118689 is a high-severity vulnerability in OvenMediaLabs OvenMediaEngine, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118689 in the wild and no public exploit code.

Affected product: OvenMediaLabs OvenMediaEngine. 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-118689/ (Markdown: https://insights.sbomify.com/CVE-2026-118689/index.md)
```

## Sources

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

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