Vulnerability in MERCURY MIPC252W v1.0.5 Build 230306 Rel.79931n (CVE-2026-51599)
Summary
Vulnerability in MERCURY MIPC252W v1.0.5 Build 230306 Rel.79931n (CVE-2026-51599). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-51599 has been found in MERCURY MIPC252W v1.0.5 Build 230306 Rel.79931n.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "MERCURY MIPC252W v1.0.5 Build 230306 Rel.79931n CVE-2026-51599" on the vendor's site.
CVE-2026-51599 (MERCURY MIPC252W v1.0.5 Build 230306 Rel.79931n) — CWE-20 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in MERCURY MIPC252W v1.0.5 Build 230306 Rel.79931n.
Check the vendor advisory for the affected versions of MERCURY MIPC252W v1.0.5 Build 230306 Rel.79931n.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで MERCURY MIPC252W v1.0.5 Build 230306 Rel.79931n を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web github.com
- web github.com