Quick answers
- Is CVE-2026-51600 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-51600 being exploited in the wild.
- How severe is CVE-2026-51600?
- Informational severity, with a CVSS score of 5.3, published 9 July 2026.
- Which products and versions are affected?
- Tenda CP3 V31.1.9.91.
- Is there a fix for CVE-2026-51600?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-51600 attacked?
- It is attacked over the network, in device firmware.
- Am I affected by CVE-2026-51600?
- Check whether you run Tenda CP3 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Tenda CP3 V3.0 (firmware V31.1.9.91) RTSP parser fails to validate the Content-Length header field during DESCRIBE, SETUP, and PLAY requests. When a request specifies a Content-Length but provides no message body, the parser enters a persistent 'body-awaiting' state. Because the device does not implement a timeout or actively close these stalled connections, it suffers from a TCP resource leak. An unauthenticated remote attacker can exploit this to exhaust available connections, leading to a permanent denial-of-service (DoS) condition for the RTSP service.
Affected products
- Tenda CP3 V3.0 V31.1.9.91
Timeline
- 2026-07-09: disclosed: Initial vulnerability disclosure and CVE assignment.
- 2026-07-09: advisory: NVD published the CVE record.