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

> An unauthenticated network-adjacent attacker can cause a denial of service on MERCURY IP cameras by sending a crafted RTSP DESCRIBE request with a malformed URL.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-g3rw-v45p-h99c

## What is CVE-2026-51598?

CVE-2026-51598 is a medium-severity denial of service vulnerability in n/a, published on 9 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An input validation vulnerability in the RTSP service of MERCURY MIPC252W IP Camera v1.0.5 Build 230306 Rel.79931n) allows an unauthenticated, network-adjacent attacker to cause a denial of service via a crafted DESCRIBE request with a malformed URL in the request line.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-51598 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-51598 is a medium-severity denial of service vulnerability in n/a, published on 9 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51598 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-51598/ (Markdown: https://insights.sbomify.com/CVE-2026-51598/index.md)
```

## Sources

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

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