{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34122 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34122 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34122 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. Tapo C520WS v2.6, published on 2 Apr 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-34122 and fix it if it is affected.\n\nWhat it is: CVE-2026-34122 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. Tapo C520WS v2.6, published on 2 Apr 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-34122 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Tapo C520WS v2.6. 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-34122/ (Markdown: https://insights.sbomify.com/CVE-2026-34122/index.md)","id":"CVE-2026-34122","markdown":"https://insights.sbomify.com/CVE-2026-34122/index.md","name":"CVE-2026-34122","record":{"aliases":["GHSA-hx8v-fm8j-mj2j"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link security camera","requires_auth":"none","summary":"An attacker can cause a denial of service on TP-Link Tapo C520WS cameras by triggering a stack-based buffer overflow via malformed configuration input.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"tapo_c520ws_firmware","vendor":"tp-link"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A stack-based buffer overflow vulnerability was identified in TP-Link Tapo C520WS v2.6 within a configuration handling component due to insufficient input validation.  An attacker can exploit this vulnerability by supplying an excessively long value for a vulnerable configuration parameter, resulting in a stack overflow.\n\nSuccessful exploitation results in Denial-of-Service (DoS) condition, leading to a service crash or device reboot, impacting availability.","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":"Stack-based Buffer Overflow Leading to Denial of Service in TP-Link Tapo C520WS","id":"CVE-2026-34122","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Whitelist Validation Bypass in TP-Link Tapo C520WS","id":"CVE-2026-34123"},"packages":[],"prev":{"headline":"Authentication Bypass in DS Configuration Service via HTTP Request Parsing Differential of TP-Link Tapo C520WS","id":"CVE-2026-34121"},"products":["Tapo C520WS v2.6"],"published":"2026-04-02","related":[{"cvss_score":8.7,"headline":"Authentication Bypass in DS Configuration Service via HTTP Request Parsing Differential of TP-Link Tapo C520WS","id":"CVE-2026-34121","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.1,"headline":"Denial-of-Service Vulnerability in RTSP Input Handling on TP-Link's Tapo C520WS","id":"CVE-2026-8714","kev_date_added":null,"published":"2026-06-05"},{"cvss_score":7.1,"headline":"Heap-based Buffer Overflow Vulnerability Leading to Denial-of-Service in TP-Link Tapo C100, C101, C210 \u0026 C520WS","id":"CVE-2026-34118","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.1,"headline":"Heap-based Buffer Overflow Vulnerability Leading to Denial-of-Service in TP-Link Tapo C520WS","id":"CVE-2026-34119","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.1,"headline":"Heap-based Buffer Overflow Vulnerability Leading to Denial-of-Service in TP-Link Tapo C520WS","id":"CVE-2026-34120","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":7.1,"headline":"Denial of Service via Path Expansion Overflow in HTTP Service in TP-Link Tapo C520WS","id":"CVE-2026-34124","kev_date_added":null,"published":"2026-04-02"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["TP-Link Systems Inc."]},"summary":"An attacker can cause a denial of service on TP-Link Tapo C520WS cameras by triggering a stack-based buffer overflow via malformed configuration input.","url":"https://insights.sbomify.com/CVE-2026-34122/"}