{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2025-15605 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-15605 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15605 is a high-severity vulnerability in TP-Link Systems Inc. Archer NX200 v1.0, published on 23 Mar 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-2025-15605 and fix it if it is affected.\n\nWhat it is: CVE-2025-15605 is a high-severity vulnerability in TP-Link Systems Inc. Archer NX200 v1.0, published on 23 Mar 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-2025-15605 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Archer NX200 v1.0. 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-2025-15605/ (Markdown: https://insights.sbomify.com/CVE-2025-15605/index.md)","id":"CVE-2025-15605","markdown":"https://insights.sbomify.com/CVE-2025-15605/index.md","name":"CVE-2025-15605","record":{"aliases":["GHSA-46q8-mxmv-wf7q"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link Archer router","requires_auth":"low_privilege","summary":"An authenticated attacker can decrypt, modify, and re-encrypt device configuration data using a hardcoded cryptographic key, compromising confidentiality and integrity.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"archer_nx200_firmware","vendor":"tp-link"},{"product":"archer_nx210_firmware","vendor":"tp-link"},{"product":"archer_nx500_firmware","vendor":"tp-link"},{"product":"archer_nx600_firmware","vendor":"tp-link"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"A hardcoded cryptographic key within the configuration mechanism on TP-Link Archer NX200, NX210, NX500 and NX600 enables decryption and re-encryption of device configuration data. An authenticated attacker may decrypt configuration files, modify them, and re-encrypt them, affecting the confidentiality and integrity of device configuration data.","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":"Hardcoded Cryptographic Key in Configuration Encryption Mechanism on TP-Link Archer NX200, NX210, NX500 and NX600","id":"CVE-2025-15605","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"Denial of Service (DoS) in HTTPD Input Handling on TP-Link TD-W8961N","id":"CVE-2025-15606"},"packages":[],"prev":{"headline":"Amon2 versions before 6.17 for Perl use an insecure random_string implementation for security functions","id":"CVE-2025-15604"},"products":["Archer NX200 v1.0","Archer NX200 v2.0","Archer NX200 v2.20","Archer NX200 v3.0","Archer NX210 v2.0 v2.20","Archer NX210 v3.0","Archer NX500 v1.0","Archer NX500 v2.0","Archer NX600 v1.0","Archer NX600 v2.0","Archer NX600 v3.0"],"published":"2026-03-23","related":[{"cvss_score":8.6,"headline":"Authorization Bypass in HTTP Server Endpoints on TP-Link Archer NX200, NX210, NX500 and NX600","id":"CVE-2025-15517","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":8.5,"headline":"Command Injection in Wireless Control CLI on TP-Link Archer NX200, NX210, NX500 and NX600","id":"CVE-2025-15518","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":8.5,"headline":"Command Injection in Modem Management CLI on TP-Link Archer NX200, NX210, NX500 and NX600","id":"CVE-2025-15519","kev_date_added":null,"published":"2026-03-23"}],"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":"total"},"state":"PUBLISHED","updated":"2026-03-24","vendors":["TP-Link Systems Inc."]},"summary":"An authenticated attacker can decrypt, modify, and re-encrypt device configuration data using a hardcoded cryptographic key, compromising confidentiality and integrity.","url":"https://insights.sbomify.com/CVE-2025-15605/"}