CVE-2026-51604
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA stack-based buffer overflow vulnerability in the RTSP service of Tenda CP3 V3.0 (firmware V31.1.9.91) allows an unauthenticated remote attacker to cause a denial of service via a crafted PLAY request.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stack-based buffer overflow vulnerability exists in the RTSP service of Tenda CP3 V3.0 IP camera (firmware V31.1.9.91). An unauthenticated remote attacker can send a specially crafted RTSP PLAY request to trigger the buffer overflow, causing denial of service. The vulnerability has a CVSS score of 7.5 (HIGH), indicating significant impact on availability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelLocate the IP camera on your network and confirm the model is Tenda CP3 V3.0. This can be done via the device's web interface, DHCP lease tables, or network scanning tools that report device make/model.Affected if The device is NOT a Tenda CP3 V3.0 model, then it is not affected by this specific vulnerability.
-
Check installed firmware versionAccess the camera's web administration interface and navigate to the System or Device Info section to view the firmware version. Alternatively, check the device documentation or backup configuration files for version information.Affected if The installed firmware version is V31.1.9.91, then the device is running the affected version.
-
Verify RTSP service statusCheck if the RTSP service is enabled on the device. This is typically found in the camera's settings under Network or Streaming configuration. You can also scan the device on port 554 to confirm RTSP is listening.Affected if RTSP service is disabled or not listening on the device, then the attack surface for this vulnerability may not be present.
-
Assess network exposure of RTSP portDetermine if port 554 (RTSP) is accessible from untrusted networks. Use network firewall rules, port scans from external IPs, or review ACLs to check if RTSP is exposed to the internet or untrusted LAN segments.Affected if RTSP port 554 is directly exposed to the internet or untrusted networks without firewall protection, then the device is vulnerable to remote exploitation.
The environment is affected if you have a Tenda CP3 V3.0 IP camera running firmware V31.1.9.91 with RTSP service enabled and accessible from untrusted networks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince the vulnerability resides in vendor firmware without an available patch, implement compensating controls: restrict or block external access to RTSP port 554, disable the RTSP service if not required, and place the device behind a firewall or VPN. Monitor for vendor firmware updates.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-51604 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-51604 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data