{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-34123 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34123 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34123 is a high-severity authentication bypass vulnerability in TP-Link Systems Inc. Tapo C520WS v2, published on 5 Jun 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-34123 and fix it if it is affected.\n\nWhat it is: CVE-2026-34123 is a high-severity authentication bypass vulnerability in TP-Link Systems Inc. Tapo C520WS v2, published on 5 Jun 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-34123 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Tapo C520WS 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-34123/ (Markdown: https://insights.sbomify.com/CVE-2026-34123/index.md)","id":"CVE-2026-34123","markdown":"https://insights.sbomify.com/CVE-2026-34123/index.md","name":"CVE-2026-34123","record":{"aliases":["GHSA-x7cf-gm5r-xq89"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link security camera","requires_auth":"low_privilege","summary":"Attackers with restricted accounts can bypass API whitelist restrictions to execute unauthorized sensitive operations, causing device resets or configuration changes.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"On Tapo\nC520WS v2, restricted accounts (for example, hub users) are intended to execute\nonly a limited set of low‑sensitivity operations. Due to a logic flaw in the\ndevice’s API authorization mechanism, an attacker can craft requests that\nleverage legitimate “method mapping” behavior to bypass whitelist restrictions,\nallowing restricted operations to be masked as permitted requests and executed.\n\nSuccessful\nexploitation may allow an attacker (with access to a restricted account) to\nexecute unauthorized sensitive operations. \nDepending on the operation invoked, impact could include device\nresets, unintended configuration changes, or disruption of normal operation,\nleading to loss of availability and integrity of the device.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Whitelist Validation Bypass in TP-Link Tapo C520WS","id":"CVE-2026-34123","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of Service via Path Expansion Overflow in HTTP Service in TP-Link Tapo C520WS","id":"CVE-2026-34124"},"packages":[],"prev":{"headline":"Stack-based Buffer Overflow Leading to Denial of Service in TP-Link Tapo C520WS","id":"CVE-2026-34122"},"products":["Tapo C520WS v2"],"published":"2026-06-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-08","vendors":["TP-Link Systems Inc."]},"summary":"Attackers with restricted accounts can bypass API whitelist restrictions to execute unauthorized sensitive operations, causing device resets or configuration changes.","url":"https://insights.sbomify.com/CVE-2026-34123/"}