LiveActive security incident?Get immediate response
CVE Record

CVE-2026-51599: An insufficient input validation vulnerability in the RTSP service of MERCURY MIPC252W v1.0.5 Build 230306...

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue affects the RTSP service on MERCURY MIPC252W firmware v1.0.5 Build 230306 Rel.79931n. A remote unauthenticated party can make an individual RTSP TCP connection stop processing normally until timeout. Public scoring marks it critical, but the described impact is connection-level disruption, so business risk depends heavily on internet exposure and camera dependence.

Executive priority

Prioritize exposed surveillance environments. If RTSP is internet-facing, treat this as urgent hardening work. If cameras are isolated on trusted networks, prioritize normal patch review and monitoring while awaiting vendor guidance.

Technical view

The RTSP parser insufficiently validates malformed request framing. When a request declares body content that is not supplied, the parser waits for body data and silently consumes later connection data until server timeout. Sources describe unauthenticated network reachability and CWE-20. The CVSS vector lists 9.8 critical, but the narrative evidence primarily supports availability impact on a single TCP connection.

Likely exposure

Organizations using MERCURY MIPC252W cameras with firmware v1.0.5 Build 230306 Rel.79931n may be exposed, especially if RTSP is reachable from untrusted networks. The supplied CVE metadata does not provide CPEs or broader affected-version ranges.

Exploitation context

No CISA KEV listing is indicated, and the provided sources do not state active exploitation. A public researcher report exists. Exploitation appears remote and unauthenticated against the RTSP service, but sources describe temporary disruption of an individual TCP connection rather than device-wide compromise.

Researcher notes

Evidence is limited to CVE metadata and a public GitHub report. The affected product is named in the title and description, while structured affected fields are not populated. No official vendor fix is provided in the supplied sources. CVSS impact claims appear broader than the described per-connection behavior.

Mitigation direction

  • Check MERCURY or device supplier guidance for firmware updates or official mitigations.
  • Remove RTSP exposure from the public internet.
  • Restrict RTSP access to trusted networks, VPNs, or management VLANs.
  • Disable RTSP where it is not operationally required.
  • Monitor camera availability and RTSP timeout anomalies.

Validation and detection

  • Inventory MERCURY MIPC252W devices and firmware versions.
  • Confirm whether firmware is v1.0.5 Build 230306 Rel.79931n.
  • Identify where RTSP is enabled and reachable.
  • Verify firewall rules block untrusted RTSP access.
  • Review logs or telemetry for unusual RTSP connection timeouts.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-51599 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-51599Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.