CVE-2026-51599
Unauthenticated malformed RTSP request causes single-connection DoS on MERCURY MIPC252W.
Is CVE-2026-51599 being exploited?
Not confirmed. CVE-2026-51599 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.63% probability of exploitation in the next 30 days.
How severe is CVE-2026-51599?
CVE-2026-51599 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-51599?
Not known from our data. No patch reference has been recorded for CVE-2026-51599, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-51599 affect?
CVE-2026-51599 affects MERCURY MIPC252W v1.0.5 Build 230306 Rel.79931n, RTSP service on affected devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-51599?
Isolate devices, block/limit RTSP (TCP 554) from untrusted networks, disable RTSP if unused, apply vendor firmware when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can send a malformed RTSP request that forces the RTSP parser to hang and silently consume subsequent data, causing denial of service for the RTSP connection/stream.
Immediate action required