{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-71960 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-71960 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-71960 is a critical vulnerability in Shenzhen Cudy Technology Co., Ltd. P5 V1.1, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-71960 and fix it if it is affected.\n\nWhat it is: CVE-2026-71960 is a critical vulnerability in Shenzhen Cudy Technology Co., Ltd. P5 V1.1, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-71960 in the wild and no public exploit code.\n\nAffected product: Shenzhen Cudy Technology Co., Ltd. P5 V1.1. 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-71960/ (Markdown: https://insights.sbomify.com/CVE-2026-71960/index.md)","id":"CVE-2026-71960","markdown":"https://insights.sbomify.com/CVE-2026-71960/index.md","name":"CVE-2026-71960","record":{"aliases":["GHSA-jw4g-pv34-hp37"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cudy WR3000 router","requires_auth":"none","summary":"Attackers can extract a hard-coded JWT secret from the firmware to forge tokens and bypass MQTT authentication, gaining unauthorized access to the router's mesh interface.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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"}],"description":"Cudy WR3000 2.0 running firmware before 2.5.24 contains a hard-coded JWT HMAC signing secret vulnerability in the Mosquitto MQTT broker's authentication plugin that allows unauthenticated attackers to forge valid JWT tokens by extracting the secret from the firmware image. Attackers can use the extracted secret to craft arbitrary JWT tokens and authenticate to the MQTT broker without legitimate credentials, gaining unauthorized access to the device's mesh networking interface.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-20","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-20T15:22:02Z","kind":"github_poc","ref":"https://github.com/Hunt-Benito/the-same-key-opens-every-box-cve-2026-71960-hard-coded-jwt-secret-in-cudy-wr3000-mesh-mqtt","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cudy WR3000 2.0 Hard-coded JWT Secret Authentication Bypass via MQTT","id":"CVE-2026-71960","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Cudy WR3000 2.0 OS Command Injection via Mesh MQTT Command Handler","id":"CVE-2026-71961"},"packages":[],"prev":{"headline":"Bitwarden Server \u003c 2026.7.2 Audit Log Injection via POST /collect","id":"CVE-2026-71959"},"products":["P5 V1.1","WR3000 2.0"],"published":"2026-08-19","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["Shenzhen Cudy Technology Co., Ltd."]},"summary":"Attackers can extract a hard-coded JWT secret from the firmware to forge tokens and bypass MQTT authentication, gaining unauthorized access to the router's mesh interface.","url":"https://insights.sbomify.com/CVE-2026-71960/"}