{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-5040 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5040 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5040 is a high-severity vulnerability in TP-Link Systems Inc. Deco M5 Deco M5 V1, published on 14 Jul 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-5040 and fix it if it is affected.\n\nWhat it is: CVE-2026-5040 is a high-severity vulnerability in TP-Link Systems Inc. Deco M5 Deco M5 V1, published on 14 Jul 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-5040 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Deco M5 Deco M5 V1. 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-5040/ (Markdown: https://insights.sbomify.com/CVE-2026-5040/index.md)","id":"CVE-2026-5040","markdown":"https://insights.sbomify.com/CVE-2026-5040/index.md","name":"CVE-2026-5040","record":{"aliases":["GHSA-6vqq-hcvj-cx94"],"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 Deco M5","requires_auth":"high_privilege","summary":"Weak password hashing in TP-Link Deco M5 allows attackers with privileged access to recover credentials via brute-force, leading to unauthorized device management access.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"deco_m5_firmware","vendor":"tp-link"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-916","name":"Use of Password Hash With Insufficient Computational Effort"}],"description":"TP-Link Deco M5 v1 uses a weak password hashing mechanism to store user credentials.  An attacker who obtains the password hash through system compromise or privileged access could perform brute-force or dictionary attacks.\n\nSuccessful exploitation may result in disclosure of authentication credentials, enabling unauthorized access to device management functions, depending on the privileges associated with the recovered password. The primary security impact is loss of confidentiality.","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":"Weak Password Hashing Mechanism in TP-Link Deco M5","id":"CVE-2026-5040","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"code-projects Chamber of Commerce Membership Management System pageMail.php fwrite command injection","id":"CVE-2026-5041"},"packages":[],"prev":{"headline":"Predictable Default Cryptographic Key Used for DES Encryption in TP-Link TL-WL841N","id":"CVE-2026-5039"},"products":["Deco M5 Deco M5 V1"],"published":"2026-07-14","related":[],"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-07-15","vendors":["TP-Link Systems Inc."]},"summary":"Weak password hashing in TP-Link Deco M5 allows attackers with privileged access to recover credentials via brute-force, leading to unauthorized device management access.","url":"https://insights.sbomify.com/CVE-2026-5040/"}