CVE-2026-51605
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.991) allows an unauthenticated remote attacker to cause a denial of service via a crafted TEARDOWN 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 exists in the RTSP service of Tenda CP3 V3.0 IP camera firmware V31.1.9.991. The vulnerability is triggered by a specially crafted TEARDOWN request sent to the RTSP service, allowing an unauthenticated remote attacker to overflow a stack-based buffer and cause a denial of service condition.
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 the device modelCheck the device label or access the web interface to confirm the model is Tenda CP3 V3.0 IP cameraAffected if Device is not a Tenda CP3 V3.0 model
-
Check the firmware versionAccess the camera's web interface (usually via HTTP on the local network) and navigate to System Settings or About page to view the firmware version. Alternatively, check via RTSP client or manufacturer utility.Affected if Firmware version is V31.1.9.991 (the affected version)
-
Verify RTSP service is enabledCheck the camera's settings for RTSP streaming functionality. This is typically found under Network Settings or Stream Settings in the web interface. RTSP is commonly enabled by default on IP cameras.Affected if RTSP service is enabled on the device
-
Confirm RTSP port accessibilityFrom an external or non-local network host, attempt to connect to the RTSP port (default 554) on the camera's IP address using a tool like telnet, netcat, or an RTSP client. Check if the port is responding.Affected if RTSP port 554 (or configured RTSP port) is accessible from an untrusted network
-
Check for service responseSend an OPTIONS or DESCRIBE RTSP request to the camera using a tool like curl or ffprobe: `ffprobe -rtsp_transport tcp rtsp://<camera_ip>:554/`Affected if The RTSP service responds to requests (indicating it is running and reachable)
The user is affected if they have a Tenda CP3 V3.0 camera running firmware V31.1.9.991 with RTSP service enabled and accessible from a network where unauthenticated attackers can reach it.
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 dataApply the vendor-supplied firmware update for Tenda CP3 V3.0 when available. As an interim measure, restrict network access to the RTSP service (typically port 554) using firewall rules or network segmentation to prevent unauthenticated attackers from reaching the service.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-51605 — 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-51605 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