HIGH 7.5

CVE-2026-51606: Tenda CP3 RTSP Denial of Service via Oversized Field Values

A vulnerability in Tenda CP3 V3.0 devices (firmware V31.1.9.91) causes the RTSP service to crash and terminate connections when it receives requests with oversized field values. Instead of properly rejecting the malformed request per protocol standards, the device sends a TCP reset (RST), disrupting legitimate video streaming traffic. An attacker on the network can trigger this denial-of-service condition by sending crafted RTSP requests without authentication.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-20
Affected products
0 configuration(s)
Published / Modified
2026-07-09 / 2026-07-10

NVD description (verbatim)

An improper input handling vulnerability in the RTSP service of Tenda CP3 V3.0 (firmware V31.1.9.91) causes the device to abruptly terminate the TCP connection with a RST packet when a request containing an oversized field value is received, without returning any RFC 2326-compliant error response. This behavior affects the request-line URL field and header field values across multiple RTSP request types.

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-51606 is an improper input validation flaw in the RTSP (Real Time Streaming Protocol) service of Tenda CP3 V3.0 running firmware V31.1.9.91. The vulnerability stems from inadequate bounds checking on the request-line URL field and header field values across multiple RTSP request types. When an oversized field is submitted, the service abruptly closes the connection with a TCP RST packet rather than returning an RFC 2326-compliant error response (such as a 431 Request Header Fields Too Large). This non-standard behavior indicates incomplete input sanitization in the protocol handler.

Business impact

The denial-of-service condition can disrupt video surveillance and streaming operations that depend on continuous RTSP connections. For organizations relying on Tenda CP3 devices for network video monitoring, recurring connection resets create service interruptions and may trigger false alerts or missed recording windows. The vulnerability requires no authentication, making it accessible to any network-adjacent attacker, which elevates risk in shared network environments or if the device is exposed to untrusted networks.

Affected systems

Tenda CP3 V3.0 devices running firmware version V31.1.9.91 are confirmed vulnerable. The improper input handling affects the RTSP service across multiple request types, so any client application or device that communicates with the CP3 via RTSP protocol is exposed to the denial-of-service condition.

Exploitability

Exploitation requires no special privileges or user interaction. An attacker must be network-adjacent (on the same network or with network access to the device's RTSP port, typically UDP 554 or TCP 554) and send a single crafted RTSP request with an oversized field value to trigger the vulnerability. The lack of authentication requirement and the ease of crafting malformed RTSP packets make this practical to exploit with readily available tools.

Remediation

Update Tenda CP3 V3.0 devices to a patched firmware version that properly implements input validation and RFC 2326-compliant error responses. Verify the availability of a firmware update from Tenda that addresses improper input handling in the RTSP service. Until patching is possible, restrict network access to the RTSP port using firewall rules or network segmentation to limit exposure to trusted sources only.

Patch guidance

Contact Tenda support or check the Tenda product security advisories page for firmware updates addressing CVE-2026-51606. Confirm that the updated firmware properly validates field sizes and returns standards-compliant error responses instead of abruptly terminating connections. Test patches in a non-production environment before deployment to ensure compatibility with your video management system and other network components.

Detection guidance

Monitor RTSP traffic for TCP RST packets sent by Tenda CP3 devices in response to legitimate requests, as this is abnormal behavior. Log and alert on repeated connection resets from the same source IP to the RTSP port. Examine RTSP request logs for oversized field values or anomalously long header strings. Network-based intrusion detection systems (IDS) can be tuned to flag RTSP requests with field values exceeding RFC 2326 limits.

Why prioritize this

With a CVSS 3.1 score of 7.5 (HIGH), this vulnerability carries significant risk due to its ease of exploitation (no authentication, low attack complexity, network-accessible), widespread impact on availability, and potential disruption of video surveillance operations. Organizations using Tenda CP3 devices in production should treat this as a near-term priority, particularly if the devices are on network segments accessible to untrusted hosts.

Risk score, explained

The CVSS 3.1 score of 7.5 reflects a high-severity availability impact (the attacker can reliably deny service), combined with a low barrier to exploitation. The attack vector is network-based with no special privileges required (PR:N), and the attack complexity is low (AC:L). There is no impact to confidentiality or integrity, limiting the score below critical, but the ability to disrupt service at scale across multiple RTSP connections justifies the HIGH severity rating.

Frequently asked questions

Can this vulnerability be exploited from outside my network?

Yes, if your RTSP port (typically 554) is accessible over the internet or reachable by an attacker on the network. However, the attacker must have network-layer access to reach the device. If your Tenda CP3 is isolated on an internal network or behind a firewall that blocks inbound RTSP traffic, external exploitation is not practical.

Does this affect all Tenda CP3 models or just V3.0?

The vulnerability is confirmed in Tenda CP3 V3.0 running firmware V31.1.9.91. Other models or firmware versions may have different code paths and may or may not be vulnerable. Check the Tenda security advisory for the complete list of affected firmware versions.

Will a standard DoS mitigation strategy protect against this?

Partially. Rate limiting or connection limits may reduce the impact of a sustained attack, but a single malformed RTSP request is sufficient to trigger the vulnerability. The best mitigation is to restrict RTSP port access via firewall rules and apply the firmware patch once available.

What RFC 2326 error response should the device return instead?

For requests with excessively large field values, RFC 2326 stipulates that the server should return a 431 Request Header Fields Too Large response (or similar 4xx error) before disconnecting. This allows the client to log the error and retry gracefully, rather than experiencing an abrupt TCP reset.

This analysis is based on the published CVE record and available vulnerability details as of July 2026. No exploit code or weaponized proof-of-concept steps are provided. Organizations should verify patch availability and compatibility with their environment before deployment. This vulnerability analysis is for informational purposes to support security decision-making and does not constitute legal advice or a guarantee of security. Always consult vendor advisories and conduct internal testing before deploying patches to production systems. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).