# CVE-2026-51599: Denial of service in n/a

> An unauthenticated remote attacker can cause a temporary denial of service on MERCURY IP cameras by sending malformed RTSP requests that hang TCP connections.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-c38f-3577-frmw

## What is CVE-2026-51599?

CVE-2026-51599 is a critical denial of service vulnerability in n/a, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An insufficient input validation vulnerability in the RTSP service of MERCURY MIPC252W v1.0.5 Build 230306 Rel.79931n allows an unauthenticated remote attacker to render an individual TCP connection temporarily unusable via sending an RTSP request with a Content-Length header but no corresponding message body. The affected RTSP parser enters a body-waiting state instead of rejecting the malformed request, causing all subsequent data on the connection to be silently consumed as body content until a server-side timeout closes the connection.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-51599 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51599 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-51599 is a critical denial of service vulnerability in n/a, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51599 exists.

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

## Sources

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

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