CVE-2026-0919
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 · uneditedThe HTTP parser of Tapo C210 v3, C220 v1 and C520WS v2 cameras improperly handles requests containing an excessively long URL path. An invalid‑URL error path continues into cleanup code that assumes allocated buffers exist, leading to a crash and service restart. An unauthenticated attacker can force repeated service crashes or device reboots, causing denial of service.
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 · high confidenceThe HTTP parser in Tapo C210 v3, C220 v1, and C520WS v2 cameras fails to properly handle requests with excessively long URL paths. When an invalid-URL error occurs, the cleanup code assumes buffers were allocated when they were not, leading to a null-pointer dereference or similar crash that restarts the service. Unauthenticated attackers can repeatedly trigger this condition to cause persistent denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.4.2< 1.2.3CVSS 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 Tapo camera modelLocate the device model number on the physical device label or check the device information page in the Tapo mobile app or web interface. Confirm it is one of: C210 v3, C220 v1, or C520WS v2.Affected if The device model is C210 v3, C220 v1, or C520WS v2.
-
Check the installed firmware versionAccess the camera settings through the Tapo app or web interface and navigate to the Device Info or Firmware section. Note the exact firmware version number.Affected if The firmware version is below 1.4.2 for C220, below 1.2.3 for C520WS, or for C210 v3 if the version is below the equivalent patched release.
-
Verify HTTP service is network-accessibleConfirm the camera is reachable over HTTP/HTTPS from the network. Attempt to access the camera IP address in a browser or use a tool like curl to send an HTTP request.Affected if The camera HTTP service is exposed on the network and reachable from untrusted segments.
-
Check for service instability or repeated restartsReview the camera system logs through the Tapo app or check network monitoring for frequent camera availability drops or unexpected reboots occurring at regular intervals.Affected if The camera service is crashing and restarting repeatedly, especially in a pattern consistent with repeated malicious requests.
-
Inspect HTTP traffic for abnormally long URL pathsUse network capture tools or WAF/IDS logs to examine HTTP requests sent to the camera. Look for requests with unusually long URL paths that may be triggering the parser error.Affected if HTTP requests with excessively long URL paths (significantly exceeding typical URL lengths) are being processed by the camera.
The environment is affected if a Tapo C210 v3, C220 v1, or C520WS v2 camera is running firmware below the patched version and has its HTTP service network-accessible, with observable crash behavior or suspicious long-URL traffic present.
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.
dbcve · scoped1.2.31.4.2
Apply vendor firmware updates when available; otherwise, implement network-level protections such as WAF rules or IDS/IPS signatures to block HTTP requests with abnormally long URL paths, and consider network segmentation to isolate affected devices.
Tapo C220: upgrade to firmware 1.4.2 | Tapo C520WS: upgrade to firmware 1.2.3
- Identify the specific Tapo camera model (C220 or C520WS) from the affected device
- Access the camera's web interface or Tapo mobile app to check the current firmware version
- Navigate to TP-Link's official support page for the specific camera model
- Download the firmware update: version 1.4.2 for Tapo C220, or version 1.2.3 for Tapo C520WS
- Follow TP-Link's standard firmware update procedure (typically via the Tapo app or web interface)
- After updating, verify the firmware version shows 1.4.2 (C220) or 1.2.3 (C520WS) to confirm the patch is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0919 — 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-0919 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