{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27126 exists.","fix":"No fix has been published for CVE-2023-27126 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-27126 is a medium-severity vulnerability in n/a, published on 6 Jun 2023. 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-2023-27126 and fix it if it is affected.\n\nWhat it is: CVE-2023-27126 is a medium-severity vulnerability in n/a, published on 6 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27126 exists.\n\nAffected product: n/a. 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-2023-27126/ (Markdown: https://insights.sbomify.com/CVE-2023-27126/index.md)","id":"CVE-2023-27126","markdown":"https://insights.sbomify.com/CVE-2023-27126/index.md","name":"CVE-2023-27126","record":{"aliases":["GHSA-jg46-gm9c-xj3p"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link security camera","requires_auth":"none","summary":"An attacker with physical access can extract hardcoded keys to decrypt Wi-Fi passwords and TP-Link account credentials from the camera.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tapo_c200_firmware","vendor":"tp-link"}],"cvss":{"score":4.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"The AES Key-IV pair used by the TP-Link TAPO C200 camera V3 (EU) on firmware version 1.1.22 Build 220725 is reused across all cameras. An attacker with physical access to a camera is able to extract and decrypt sensitive data containing the Wifi password and the TP-LINK account credential of the victim.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2023-27126","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-27130"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-27121"},"products":["n/a"],"published":"2023-06-06","related":[{"cvss_score":9.8,"headline":"TP-LINK Tapo C200 remote code execution vulnerability","id":"CVE-2021-4045","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":8.7,"headline":"Unauthenticated Access to connectAP API Endpoint on Tapo C100, C200 \u0026 C425","id":"CVE-2025-14300","kev_date_added":null,"published":"2025-12-20"},{"cvss_score":8.7,"headline":"Remote Code Execution via Stack-based Buffer Overflow in ONVIF SOAP Parser in TP-Link Tapo C200 and C520WS","id":"CVE-2025-8065","kev_date_added":null,"published":"2025-12-20"},{"cvss_score":7.1,"headline":"Denial-of-Service via Oversized Encrypted Credential Input in TP-Link Tapo C200","id":"CVE-2026-15316","kev_date_added":null,"published":"2026-08-18"},{"cvss_score":7.1,"headline":"Denial-of-Service Vulnerability via Malformed IPv4 Fragmentation Handling in TP-Link Tapo C200","id":"CVE-2026-12760","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":7.1,"headline":"Authenticated Stack-based Buffer Overflow in RTSP Authentication of Tapo C200","id":"CVE-2026-1871","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":7.1,"headline":"Improper Content-Length Validation in HTTPS Requests on Tapo C200","id":"CVE-2025-14299","kev_date_added":null,"published":"2025-12-20"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"An attacker with physical access can extract hardcoded keys to decrypt Wi-Fi passwords and TP-Link account credentials from the camera.","url":"https://insights.sbomify.com/CVE-2023-27126/"}