{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-0651 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-0651 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-0651 is a medium-severity path traversal vulnerability in TP Link Systems Inc. Tapo C211 v2, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-0651 and fix it if it is affected.\n\nWhat it is: CVE-2026-0651 is a medium-severity path traversal vulnerability in TP Link Systems Inc. Tapo C211 v2, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-0651 in the wild and no public exploit code.\n\nAffected product: TP Link Systems Inc. Tapo C211 v2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-0651/ (Markdown: https://insights.sbomify.com/CVE-2026-0651/index.md)","id":"CVE-2026-0651","markdown":"https://insights.sbomify.com/CVE-2026-0651/index.md","name":"CVE-2026-0651","record":{"aliases":["GHSA-c348-hjj9-x39v"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link Tapo camera","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit a path traversal flaw in TP-Link Tapo cameras to read sensitive system files and credentials via crafted URL-encoded requests.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"tapo_c260_firmware","vendor":"tp-link"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A path traversal vulnerability was identified TP-Link Tapo C260 v1, D235 v1, C211 v2 and C520WS v2.6 within the HTTP server’s handling of GET requests. The server performs path normalization before fully decoding URL encoded input and falls back to using the raw path when normalization fails. An attacker can exploit this logic flaw by supplying crafted, URL encoded traversal sequences that bypass directory restrictions and allow access to files outside the intended web root. \n\nSuccessful exploitation may allow authenticated attackers to get disclosure of sensitive system files and credentials, while unauthenticated attackers may gain access to non-sensitive static assets.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-03-06","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-03-06T16:26:00Z","kind":"github_poc","ref":"https://github.com/l0lsec/tapo-c260-rce","stars":2,"title":"PoC exploit chain for TP-Link Tapo C260 camera — CVE-2026-0651/0652/0653. Research by @spaceraccoon."}],"tier":"poc_unverified"},"has_fix":null,"headline":"Path Traversal on TP-Link Tapo D235, C211, C520WS and C260 via Local https","id":"CVE-2026-0651","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Remote Code Execution on TP-Link Tapo C260 by Guest User","id":"CVE-2026-0652"},"packages":[],"prev":{"headline":"OpenFlagr \u003c= 1.1.18 Authentication Bypass via Prefix Whitelist Path Normalization","id":"CVE-2026-0650"},"products":["Tapo C211 v2","Tapo C260 v1","Tapo C520WS v2.6","Tapo D235 v1"],"published":"2026-02-10","related":[{"cvss_score":8.7,"headline":"Remote Code Execution on TP-Link Tapo C260 by Guest User","id":"CVE-2026-0652","kev_date_added":null,"published":"2026-02-10"},{"cvss_score":7.2,"headline":"Insecure Access Control on TP-Link Tapo D235 and C260","id":"CVE-2026-0653","kev_date_added":null,"published":"2026-02-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-04","vendors":["TP Link Systems Inc.","TP-Link Systems Inc."]},"summary":"Authenticated attackers can exploit a path traversal flaw in TP-Link Tapo cameras to read sensitive system files and credentials via crafted URL-encoded requests.","url":"https://insights.sbomify.com/CVE-2026-0651/"}